FAQ

Frequently asked questions about pgpulse.

Does pgpulse read my table data?

No. pgpulse only collects telemetry and performance metadata. We read system catalogs (like pg_stat_statements and pg_stat_activity) but we never access the actual row-level content of your tables.

Will pgpulse impact my database performance?

The impact is negligible. pgpulse uses standard Postgres telemetry functions that are designed to be extremely lightweight. We collect data at a regular interval that provides high resolution without taxing your CPU.

Does it work with Supabase?

Yes. pgpulse is optimized for Supabase. We understand Supabase-specific patterns like the built-in connection poolers (PgBouncer/Supavisor) and the resource limits of different instance tiers.

How long until I see metrics?

Once you connect your database, you should see the first set of "Golden Signals" within 2 minutes. Deeper query insights and advisory items may take 10–15 minutes to aggregate enough data to be meaningful.

Can I disable specific features?

Yes. You can toggle specific collection categories (like detailed query plans) from the Settings menu in the pgpulse app.

How do I get support?

Join our Discord or email us at support@pgpulse.io for any technical questions or feedback.