Hosted PostgreSQL: supported native backend self-identity and build provenance? #52299
Unanswered
Unshakeables
asked this question in
Questions
Replies: 0 comments
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.
Does Supabase's existing hosted PostgreSQL offering currently support supplying a native operation that takes no caller-selected identity or expected value and reads only its executing physical backend's own native PID and full original backend start timestamp?
It must preserve full native precision; a fresh clock sample, other-session lookup or supplied/reduced value would not meet the requirement. Runtime callers must remain non-superuser, without row-security bypass, broad statistics access, added application-role privileges or installation/replacement powers.
For an already available supported route:
Please identify the applicable hosted offering, date/version and lifecycle limits, with provider-maintained policy or an attributable provider technical determination. Distinguish current support for this native capability from preinstalled-extension enablement, SQL/TLE distribution, self-hosted recipes and future feature requests or discretionary vetting. This is an offering-level evidence question, not a request to inspect an account, create a feature or enable anything.
All reactions