Skip to content

Place Supabase pg_stat_statements in extensions schema #747

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jingsam wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

Place Supabase pg_stat_statements in extensions schema #747

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion conf/supabase.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,7 +226,6 @@ all:
pg_safeguard: false # prevent purging running postgres instance?
pg_default_schemas: [ monitor, extensions ] # add new schema: extensions
pg_default_extensions: # default extensions to be created
- { name: pg_stat_statements ,schema: monitor }
- { name: pgstattuple ,schema: monitor }
- { name: pg_buffercache ,schema: monitor }
- { name: pageinspect ,schema: monitor }
Expand All @@ -243,6 +242,7 @@ all:
- { name: intagg ,schema: extensions }
- { name: intarray ,schema: extensions }
- { name: pg_repack ,schema: extensions }
- { name: pg_stat_statements ,schema: extensions }
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep pg_stat_statements reachable for pg_exporter

When Supabase uses the bundled PostgreSQL monitoring, this creates pg_stat_statements only in extensions, but the generated init SQL still sets the monitor user search path to monitor,public (roles/pgsql/templates/pg-init-template.sql:111) and pg_exporter connects as that user (roles/pg_monitor/templates/pg_exporter.env:7) while running unqualified FROM pg_stat_statements(false) queries (roles/pg_monitor/templates/pg_exporter.yml:1331). Those collector queries will fail with “function does not exist” for Supabase deployments unless the monitor search path is also updated or the exporter queries are schema-qualified, so query-performance metrics are lost.

Useful? React with 👍 / 👎.


#----------------------------------------------#
# BACKUP : https://pigsty.io/docs/pgsql/backup
Expand Down