Replies: 2 comments 2 replies
|
Thanks. I already checked pg_roles.rolconfig for the authenticator role, as
well as pg_db_role_setting, and there is no pgrst.db_pre_request entry.
I also checked:
- role-level settings
- database-level settings
- role + database settings
- current_setting('pgrst.db_pre_request', true)
- pg_proc.proconfig
All are absent or null.
My remaining question is specifically about the effective runtime PostgREST
configuration:
If db_pre_request were supplied through a PostgREST environment variable,
config file, or another service-level configuration managed by Supabase,
would there be any supported read-only way for a project owner to see that
effective value?
Or, if the PostgreSQL settings are absent, is it safe on hosted Supabase to
conclude that db_pre_request is effectively unset?
Thanks.
Le lun. 2 nov. 2026, 13:57, GaryAustin1 ***@***.***> a écrit :
… SELECT unnest(rolconfig) AS settingFROM pg_rolesWHERE rolname = 'authenticator';
Will return it if set.
Image: image (view on web)
<https://github.com/user-attachments/assets/981c9c98-9150-4f2e-aa9f-5eb39f1494b7>
—
Reply to this email directly, view it on GitHub
<#52625?email_source=notifications&email_token=BMSJB5RPXROFRI3RIIVOELL5XCHGBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTGUZDGMJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-19352310>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BMSJB5TSYVOHN4CIUPQSJDT5XCHGBAVCNFSNUABIKJSXA33TNF2G64TZHMZDCNBVHA3TCOJTHNCGS43DOVZXG2LPNY5TCMJSGA2TSNZSUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/BMSJB5RAPCKEAJUXXSS7Y5L5XCHGBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTGUZDGMJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVJTG633UMVZF62LPOM>
and Android
<https://github.com/notifications/mobile/android/BMSJB5WKNITXTVFKEIMDUBL5XCHGBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJTGUZDGMJQUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVZTG633UMVZF6YLOMRZG62LE>.
Download it today!
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Hi,
I need to confirm the effective PostgREST configuration for a Supabase project, without making any changes to the project.
I need to determine the effective value currently loaded for:
"db-pre-request" / "pgrst.db_pre_request"
I have already checked, read-only:
However, I understand that PostgREST may also receive configuration from other sources such as environment variables or service configuration.
My question is:
Is there a supported read-only way in Supabase to determine the effective runtime value of "db_pre_request" currently loaded by PostgREST?
I do not want to modify the project or reload PostgREST.
Please do not request or expose any JWT secret, API key, token, Authorization header, or other secret.
Thanks.
All reactions