 PostgreSQL | Autovacuum falling behind causing bloatMy PostgreSQL tables are showing 40% bloat and autovacuum doesn't seem to be keeping up with our high-update workload. Should I tune autovacuum settings, run manual VACUUM, or is there a blocking transaction preventing cleanup? | Incident Response | warning | A- | A- | 2,380vs1,591 | 41.2svs31.8s | 9vs5 | 3vs1 | 0vs0 | 3,065 charsvs3,506 chars |
| PostgreSQL | Cache hit ratio degradationMy PostgreSQL cache hit ratio has dropped from 99% to 85% over the past week. Is this a sign I need to increase shared_buffers, or could it be caused by new queries doing full table scans? | Proactive Health | warning | B+ | A- | 1,310vs1,296 | 24.9svs25.2s | 6vs5 | 2vs1 | 0vs0 | 2,728 charsvs2,996 chars |
| PostgreSQL | Connection pool exhaustion under loadMy PostgreSQL database is rejecting new connections with 'too many connections' errors. Current connections are at 95 out of 100. Should I increase max_connections or is this masking a connection leak in my application? | Incident Response | critical | B+ | A- | 601vs852 | 15.9svs19.1s | 2vs2 | 0vs0 | 0vs0 | 1,490 charsvs2,053 chars |
| PostgreSQL | Cost optimization through performance tuningMy monthly AWS RDS PostgreSQL bill is $8,000 and I need to reduce costs by 30% without degrading performance. Help me identify whether I should optimize slow queries to downgrade my instance, tune autovacuum to reduce IOPS costs, or consolidate databases. | Cost Optimization | info | C+ | B- | 1,437vs1,648 | 30.0svs36.2s | 7vs7 | 2vs2 | 0vs0 | 1,558 charsvs1,310 chars |
| PostgreSQL | Cross-platform metric mapping for PostgreSQLI'm migrating my PostgreSQL monitoring from Datadog to Prometheus. How do Datadog's postgresql.connections metric and AWS CloudWatch's DatabaseConnections metric map to the postgres_exporter metrics in Prometheus? | Cross Platform | info | A- | B+ | 868vs1,109 | 18.1svs44.1s | 2vs8 | 0vs3 | 0vs2 | 2,078 charsvs1,818 chars |
| PostgreSQL | Disk space exhaustion from WAL filesMy PostgreSQL pg_wal directory is consuming 80% of available disk space and growing. I have replication configured—how do I safely clean this up without breaking replication or causing data loss? | Incident Response | critical | B+ | A- | 1,273vs1,355 | 25.4svs24.6s | 2vs2 | 0vs0 | 0vs0 | 3,427 charsvs3,755 chars |
| PostgreSQL | Index bloat requiring maintenanceMy PostgreSQL indexes are showing significant bloat (>30%) on several high-traffic tables. Should I run REINDEX CONCURRENTLY or use pg_repack, and how do I avoid locking out my production workload? | Proactive Health | warning | B+ | A- | 1,348vs1,673 | 26.7svs32.6s | 2vs2 | 0vs0 | 0vs0 | 3,842 charsvs4,874 chars |
| PostgreSQL | Lock contention blocking transactionsMy PostgreSQL database has queries backing up because they're waiting on locks. Help me identify which queries are holding locks, which are blocked, and whether I have a deadlock situation or just long-running DDL. | Incident Response | warning | B | B+ | 1,386vs2,677 | 21.2svs39.9s | 2vs5 | 0vs1 | 0vs0 | 4,012 charsvs1,745 chars |
| PostgreSQL | Operational readiness reviewI set up Postgres a while ago. The workload has evolved a lot since then. How do I make sure it's well configured and provisioned? | Proactive Health | info | B+ | A- | 1,123vs2,515 | 23.4svs49.3s | 7vs23 | 3vs13 | 0vs3 | 2,386 charsvs3,590 chars |
| PostgreSQL | PostgreSQL migration from AWS RDS to Google Cloud SQLI'm planning to migrate our PostgreSQL database from AWS RDS to Google Cloud SQL. What are the key differences in monitoring capabilities, performance characteristics, and operational features I need to account for during and after the migration? | Migration | info | B+ | A- | 1,196vs1,278 | 26.9svs47.1s | 2vs2 | 0vs0 | 0vs0 | 4,007 charsvs4,545 chars |
| PostgreSQL | Replication lag threatening data consistencyMy PostgreSQL read replicas are falling behind the primary by 30 seconds and climbing. Help me diagnose if this is a resource bottleneck, network issue, or replication slot problem before it causes an outage. | Incident Response | critical | B+ | A- | 7,911vs6,796 | 12.2mvs1.8m | 13vs12 | 6vs6 | 0vs0 | 2,654 charsvs2,942 chars |
| PostgreSQL | Right-sizing PostgreSQL cloud instancesHelp me determine whether my Postgres deployment on Google Cloud SQL should be provisioned up or down based on my current workload. I'm seeing 45% CPU utilization on average but occasional spikes to 85%. | Capacity Planning | info | D+ | B+ | 1,162vs813 | 25.1svs18.8s | 6vs2 | 2vs0 | 0vs0 | 128 charsvs1,648 chars |
| PostgreSQL | Slow query performance investigationSeveral of my PostgreSQL queries have gotten significantly slower over the past month. Help me identify the top offenders and determine whether this needs new indexes, query rewrites, or updated table statistics. | Proactive Health | warning | A- | C+ | 6,431vs1,553 | 1.8mvs12.4m | 16vs18 | 9vs9 | 0vs2 | 3,872 charsvs1,679 chars |
| PostgreSQL | Transaction ID wraparound emergency approachingMy PostgreSQL database is showing warnings about transaction ID wraparound with age at 1.8 billion. How urgent is this, what happens if I hit the limit, and what's the safest way to prevent emergency autovacuum or shutdown? | Incident Response | critical | B+ | A- | 1,098vs814 | 24.3svs18.7s | 2vs2 | 0vs0 | 0vs0 | 2,971 charsvs2,097 chars |