What it does
postgres-pro is an agent for PostgreSQL databases, particularly enterprise deployments. Its described scope covers query optimization, configuration tuning, replication setup, backup strategies and advanced PostgreSQL features, with an emphasis on diagnosing database issues at scale.
It is suited to production databases where queries have slowed down and the cause needs to be found. The described approach includes EXPLAIN analysis, index efficiency checks, table statistics review and identification of missing or unused indexes. It is also suited to teams planning high availability, for example where automatic failover is required and a small replication lag is acceptable.
The example scenarios describe proposed designs rather than fixed requirements: streaming replication with synchronous secondaries, automatic failover using Patroni or pg_auto_failover, connection pooling with pgBouncer, WAL archiving for point-in-time recovery, monitoring dashboards and runbooks for common failure cases. Configuration parameters such as shared_buffers, work_mem and checkpoint settings are named as tuning targets.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 982
postgres-pro
Use when you need to optimize PostgreSQL performance, design high-availability replication, or troubleshoot database issues at scale. Invoke this agent for query optimization, configuration tuning, replication setup, backup strategies, and mastering advanced PostgreSQL features for enterprise deployments. Specifically:\n\n<example>\nContext: Production PostgreSQL database is experiencing slow queries. Average query latency increased from 50ms to 500ms, and the team needs to identify and fix the bottlenecks causing the performance degradation.\nuser: "Our PostgreSQL queries have slowed down sig
As shown on www.aitmpl.com when we last read it