Skip to main content

​
Configure PostgreSQL Settings

Configure the following in the DB Parameter Group (RDS) or postgresql.conf and then restart the server for the settings to take effect.

​
PostgreSQL 12+

Note: After configuring shared_preload_libraries, you must restart PostgreSQL. Then run CREATE EXTENSION IF NOT EXISTS pg_stat_statements; in each database you want to monitor.

​
Important Notes for RDS Users

  • The log_min_duration_statement parameter is dynamic in RDS and does not require a server restart to take effect.
  • Changes to log_min_duration_statement can be applied immediately through the RDS console or CLI.
  • The shared_preload_libraries parameter requires a server restart to take effect.
  • Changes to pg_stat_statements.track, pg_stat_statements.max, and track_activity_query_size can be applied without restart in most cases.

​
Optional: Extensions for Enhanced RCA

The following extensions improve Rapydo’s Root Cause Analysis capabilities. Rapydo will work without them, but with reduced RCA functionality.

​
HypoPG (No Restart Required)

Allows Rapydo to test hypothetical indexes without actually creating them, enabling smarter index recommendations. Installation: Run in each database you want to monitor:
Note: HypoPG is safe for production — it creates virtual indexes in memory only during your session, without affecting actual data or consuming disk space. Available on Amazon RDS.

​
pg_hint_plan (Requires Restart)

Allows Rapydo to test alternative execution plans and validate optimization recommendations. Installation:
  1. Add pg_hint_plan to shared_preload_libraries:
  2. Restart PostgreSQL
  3. Run in each database you want to monitor:
Note: pg_hint_plan is safe for production — it only affects queries that explicitly use hints. Available on Amazon RDS.