Skip to main content

How to Act on Recommendations

Shipping database changes requires care. Here is the recommended workflow for acting on pgpulse advisories.

1. Confirm the Issue​

Don't just blindly follow the advice. Look at the linked telemetry and queries in pgpulse to understand why the recommendation was made. Does it match your current application context?

2. Test in Staging​

Always try out the proposed fix (like a new index or a query rewrite) in a staging environment that mimics your production data volume.

  • Use EXPLAIN ANALYZE to verify the plan change.
  • Measure the latency improvement.

3. Ship Safely​

  • For schema changes (indexes, constraints), use migration tools that support zero-downtime operations.
  • Postgres Tip: Use CREATE INDEX CONCURRENTLY.
  • Supabase Tip: Check your migration statements for long locks that might block other operations.

4. Monitor Impact​

After shipping, go back to pgpulse. You should see a corresponding drop in the "Total Time" for the target queries or a reduction in the Golden Signal that triggered the warning.

Have a Rollback Plan​

Even simple indexes can occasionally cause issues (like increased write latency). Always know how to quickly revert your change if performance degrades.