-
-
Notifications
You must be signed in to change notification settings - Fork 246
fix(tests): split prime.sql so non-superuser harnesses can source it #2175
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.
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
Changes from 2 commits
2934984
4279bcd
63491bb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| -- Superuser-only extensions for testing. | ||
| -- | ||
| -- These extensions are excluded from `supautils.privileged_extensions` (see | ||
| -- the "omitted because may be unsafe" comment in | ||
| -- `ansible/files/postgresql_config/supautils.conf.j2`). Hosted Supabase | ||
| -- projects cannot install them via non-superuser sessions, so this file is | ||
| -- loaded only by superuser-context harnesses: pg_regress (nix/checks.nix), | ||
| -- the docker-image-test, and the local migrate-tool. supadev's hosted | ||
| -- engines-with-smoke test sources `prime.sql` only. | ||
| -- | ||
| -- Keep this list in sync with the "may be unsafe" list in supautils.conf.j2. | ||
|
|
||
| set client_min_messages = warning; | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. looking at j2 file it has: You're missing
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Both
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yeah thats cool to do. I have created a Linear task to take that up in next PR: https://linear.app/supabase/issue/PSQL-1265/ |
||
| create extension if not exists amcheck; | ||
| create extension if not exists file_fdw; | ||
| create extension if not exists lo; | ||
| create extension if not exists pageinspect; | ||
| create extension if not exists pg_freespacemap; | ||
| create extension if not exists pg_surgery; | ||
| create extension if not exists pg_visibility; | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
absent an automated way to ensure this, I usually like to mirror this sort of comment in the other file so that hopefully when it gets updated someone sees it and will do the right thing here (🤞)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mmlb Thanks. Taken care in latest revision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
well thats pretty terrible now that I look at it. Was hoping for an
excludelist or something :D. Guess we'll just deal with it for now.