Hosted PostgreSQL: supported native backend self-identity and build provenance?
The user is inquiring about Supabase's hosted PostgreSQL capabilities regarding native operations that identify the executing backend's PID and start timestamp. They seek details on authorization, maintenance responsibilities, and provenance mechanisms without requiring superuser privileges or additional roles. The inquiry is about existing support rather than a feature request.