2
add option to hide PgBouncer log statements
Source: supabase/supabase#34312 · opened by @anngbaum
since March 13 our Postgres logs have been spammed with RAISE WARNING from pg_bouncer.
I'm not sure what exactly triggered that change, but it's made it hard to monitor the health of our logs from a quick glance.
I have no idea if that does in fact require a warning and is something to be investigated further because of the frequency, but if the auth request is routine and not cause for concern it would be nice to exclude it from the Postgres logs view?
I would assume the options are to either just use RAISE NOTICE instead, or just add an (optional) filter to the logs view in order to hide routine events (seems per the comments [here]( this would classify as routine?)
<img width="764" alt="Screenshot 2025-03-19 at 9 15 22 AM" src=" />
I'm not sure what exactly triggered that change, but it's made it hard to monitor the health of our logs from a quick glance.
I have no idea if that does in fact require a warning and is something to be investigated further because of the frequency, but if the auth request is routine and not cause for concern it would be nice to exclude it from the Postgres logs view?
I would assume the options are to either just use RAISE NOTICE instead, or just add an (optional) filter to the logs view in order to hide routine events (seems per the comments [here]( this would classify as routine?)
<img width="764" alt="Screenshot 2025-03-19 at 9 15 22 AM" src=" />
No pledges yet. Be the first to back this.
Comments
Similar requests
Better formatting of SQL statements for RLS policies review?
2 votes · 0 comments
1-Click PgBouncer Installation - Connection Pooler for PostgreSQL
1 vote · 0 comments
Export SQL statements in Table Editor
9 votes · 0 comments
Multiple foreign tables in a single "or" statement
14 votes · 0 comments
Add necessary query params to POSTGRES_PRISMA_URL for Vercel integration
2 votes · 0 comments
No comments yet.