feat: Add support for AWS RDS deployment and enhance maintenance scheduling documentation with pg_cron and Systemd Timer options.

postgresql/procedures/README.md

@@ -28,6 +28,22 @@ The installation is performed by executing the SQL procedures in the following o
 4.  Enable partitioning on tables (`03_enable_partitioning.sql`).
 5.  Install monitoring views (`04_monitoring_view.sql`).
 
+**Command Example:**
+You can deploy these scripts manually against your Zabbix database using `psql`. Navigate to the `procedures/` directory and run:
+
+```bash
+# Connect as the zabbix database user
+export PGPASSWORD="your_zabbix_password"
+DB_HOST="localhost" # Or your RDS endpoint
+DB_NAME="zabbix"
+DB_USER="zabbix"
+
+for script in 00_partitions_init.sql 01_auditlog_prep.sql 02_maintenance.sql 03_enable_partitioning.sql 04_monitoring_view.sql; do
+    echo "Applying $script..."
+    psql -h $DB_HOST -U $DB_USER -d $DB_NAME -f "$script"
+done
+```
+
 ## Configuration
 
 Partitioning policies are defined in the `partitions.config` table.
@@ -61,7 +77,7 @@ This procedure should be scheduled to run periodically (e.g., daily via `pg_cron
 ```sql
 CALL partitions.run_maintenance();
 ```
-### Automatic Maintenance (Cron)
+### Scheduling Maintenance
 
 To ensure partitions are created in advance and old data is cleaned up, the maintenance procedure should be scheduled to run automatically. 
 
@@ -69,6 +85,73 @@ It is recommended to run the maintenance **twice a day** (e.g., at 05:30 and 23:
 *   **Primary Run**: Creates new future partitions and drops old ones.
 *   **Secondary Run**: Acts as a safety check. Since the procedure is idempotent (safe to run multiple times), a second run ensures everything is consistent if the first run failed or was interrupted.
 
+You can schedule this using one of the following methods:
+
+#### Option 1: `pg_cron` (Recommended)
+`pg_cron` is a cron-based job scheduler that runs directly inside the database as an extension.
+
+**Setup `pg_cron`:**
+1. Install the package via your OS package manager (e.g., `postgresql-15-cron` on Debian/Ubuntu, or `pg_cron_15` on RHEL/CentOS).
+2. Configure it modifying `postgresql.conf`:
+   ```ini
+   shared_preload_libraries = 'pg_cron'
+   cron.database_name = 'zabbix' # Define the database where pg_cron will run
+   ```
+3. Restart PostgreSQL:
+   ```bash
+   systemctl restart postgresql
+   ```
+4. Connect to your `zabbix` database as a superuser and create the extension:
+   ```sql
+   CREATE EXTENSION pg_cron;
+   ```
+5. Schedule the job to run:
+   ```sql
+   SELECT cron.schedule('zabbix_partition_maintenance', '30 5,23 * * *', 'CALL partitions.run_maintenance();');
+   ```
+6. **Manage your `pg_cron` jobs** (run as superuser):
+   - To **list all active schedules**: `SELECT * FROM cron.job;`
+   - To **view execution logs/history**: `SELECT * FROM cron.job_run_details;`
+   - To **remove/unschedule** the job: `SELECT cron.unschedule('zabbix_partition_maintenance');`
+
+#### Option 2: Systemd Timers
+Systemd timers provide better logging and error handling properties than standard cron.
+
+1. Create a service file **`/etc/systemd/system/zabbix-partitions.service`**:
+   ```ini
+   [Unit]
+   Description=Zabbix PostgreSQL Partition Maintenance
+   After=network.target postgresql.service
+   
+   [Service]
+   Type=oneshot
+   User=postgres
+   ExecStart=/usr/bin/psql -d zabbix -c "CALL partitions.run_maintenance();"
+   ```
+
+2. Create a timer file **`/etc/systemd/system/zabbix-partitions.timer`**:
+   ```ini
+   [Unit]
+   Description=Run Zabbix Partition Maintenance Twice Daily
+   
+   [Timer]
+   OnCalendar=*-*-* 05:30:00
+   OnCalendar=*-*-* 23:30:00
+   Persistent=true
+   
+   [Install]
+   WantedBy=timers.target
+   ```
+
+3. Enable and start the timer:
+   ```bash
+   systemctl daemon-reload
+   systemctl enable --now zabbix-partitions.timer
+   ```
+
+#### Option 3: System Cron (`crontab`)
+Standard system cron is a simple fallback.
+
 **Example Crontab Entry (`crontab -e`):**
 ```bash
 # Run Zabbix partition maintenance twice daily (5:30 AM and 5:30 PM)
@@ -76,7 +159,7 @@ It is recommended to run the maintenance **twice a day** (e.g., at 05:30 and 23:
 ```
 
 **Docker Environment:**
-If running in Docker, you can execute it via the container:
+If running in Docker, you can execute it via the host's cron by targeting the container:
 ```bash
 30 5,23 * * * docker exec zabbix-db-test psql -U zabbix -d zabbix -c "CALL partitions.run_maintenance();"
 ```