Everything you need to know before, during, and after your session — so you get maximum value on day one.
PGFlare needs a read-only AWS IAM role to connect to your RDS instance. This takes about 10 minutes using our setup guide — no write permissions, no data access.
This PostgreSQL extension captures query execution statistics and is essential for identifying slow queries. It's very low overhead and should already be enabled on most production instances.
SELECT * FROM pg_extension WHERE extname = 'pg_stat_statements';
shared_preload_libraries = 'pg_stat_statements'
The more context you give us before we start, the faster we can focus the analysis on what matters most to your business.
We read this from AWS directly, but sending ahead speeds up the briefing call.
Quick call to confirm scope, priority symptoms, and any recent changes. Not required for standard Diagnostic sessions but recommended if you have specific urgency.
We verify IAM access, confirm pg_stat_statements is populated, pull baseline metrics from CloudWatch (CPU, IOPS, connections), and run initial query analysis against pg_stat_statements and pg_stat_user_tables.
EXPLAIN ANALYZE on top queries by total_time, autovacuum config vs. table dead tuple rates, index usage analysis, lock contention review, connection pool assessment, bloat calculation. For Remediation+ sessions, remediation actions begin now in a maintenance window you specify.
All findings ranked by business impact (cost saving + performance gain). Each finding includes severity, estimated impact, and the specific SQL or config change required. No vague recommendations — everything is actionable.
Full written report delivered by end of day. We're available for a 30-minute debrief call the same day or next morning to walk through findings with your team.
Every issue is ranked by estimated monthly cost saving or P99 latency reduction so your team knows exactly what to fix first. Typical reports include 8–20 findings.
Each finding includes the specific SQL (CREATE INDEX CONCURRENTLY, VACUUM ANALYZE, ALTER SYSTEM) or parameter group value to change. Nothing to interpret — just review and apply.
Where CPU utilisation can be reduced below 50%, we recommend a specific target instance class with projected monthly saving. Includes safe-migration runbook.
CloudWatch alarm thresholds for the specific metrics that matter for your workload — autovacuum lag, connection count, wait events, and query latency buckets.
No. PGFlare operates exclusively via read-only AWS IAM. We can read RDS metadata, CloudWatch metrics, and pg_stat_statements but cannot write to your database or read your data. For Remediation+ sessions, you apply the SQL changes — we prepare them and guide you.
The Diagnostic session is entirely read-only — zero risk. Remediation+ changes are designed for
zero-downtime application: CREATE INDEX CONCURRENTLY
rather than CREATE INDEX,
parameter changes staged via RDS parameter groups rather than immediate restarts.
We always flag changes that require a maintenance window.
We'll note it in the pre-session call and can still analyse table bloat, autovacuum config, index usage, and lock contention. However, query-level analysis requires pg_stat_statements and the report will be less specific on query-level findings. We strongly recommend enabling it beforehand — see the setup guide.
Immediate improvements are typical: adding a missing index (CONCURRENTLY) shows measurable query speedup in minutes. Autovacuum tuning typically shows CPU reduction within 24 hours. Instance right-sizing is usually possible within 2-3 weeks after applying the report findings.
Yes. PGFlare operates as a GDPR-compliant data processor under UK GDPR. A signed DPA is available within 24 hours of request. See our Compliance & Security page for full details.
You pay for the deliverable — not the hours. If we complete a Diagnostic in two hours because your instance's top issues are clear-cut, you still receive the same written priority report and pay £497. If a Remediation+ session runs efficiently, you still pay £897 for all agreed fixes applied and documented. There are no time-overrun charges and no minimum billable hours for flat-fee sessions. The session ends when the deliverable is complete — not when a clock runs out.
We stand behind the quality of our analysis. If your Diagnostic session produces fewer than 5 actionable findings, or if the projected savings don't justify the session cost, we'll extend the analysis at no charge. Email [email protected] within 48 hours of report delivery.