Re: POC: Carefully exposing information without authentication

2025-05-30 Thread Greg Sabino Mullane
On Fri, May 30, 2025 at 9:34 PM Tom Lane wrote: > I think calling it in the postmaster is a nonstarter. Thanks for the feedback. Please find attached version two, which moves the code to the very start of BackendInitialize in tcop/backend_startup.c. If we handle the request, we simply proc_exit

Re: POC: Carefully exposing information without authentication

2025-05-30 Thread Tom Lane
Greg Sabino Mullane writes: > Good question. Forking is expensive, and there is also a lot of > housekeeping associated with it that is simply not needed here. We want > this to be lightweight, and simple. No need to fork if we are just going to > do a few strncmp() calls and a send(). send() can

Re: POC: Carefully exposing information without authentication

2025-05-30 Thread Greg Sabino Mullane
On Fri, May 30, 2025 at 11:02 AM Antonin Houska wrote: > Why is it important not to fork? Good question. Forking is expensive, and there is also a lot of housekeeping associated with it that is simply not needed here. We want this to be lightweight, and simple. No need to fork if we are just go

Re: POC: Carefully exposing information without authentication

2025-05-30 Thread Antonin Houska
Greg Sabino Mullane wrote: > Proposal: Allow a carefully curated selection of information to be shown > without authentication. > > A common task for an HA system or a load balancer is to quickly determine > which of your Postgres clusters is the primary, and which are the > replicas. The cano

POC: Carefully exposing information without authentication

2025-05-29 Thread Greg Sabino Mullane
Proposal: Allow a carefully curated selection of information to be shown without authentication. A common task for an HA system or a load balancer is to quickly determine which of your Postgres clusters is the primary, and which are the replicas. The canonical way to do this is to log in to each s