Re: POC: Carefully exposing information without authentication - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: POC: Carefully exposing information without authentication
Date
Msg-id CAKAnmm+-+2aZiK-wtwSCEpfOJbU7-PnwofByhr0F_XQB4wUJNw@mail.gmail.com
Whole thread Raw
In response to Re: POC: Carefully exposing information without authentication  (Antonin Houska <ah@cybertec.at>)
List pgsql-hackers
On Fri, Jan 9, 2026 at 8:56 AM Antonin Houska <ah@cybertec.at> wrote:
1. Add a new field to the PGconn structure

This kind of defeats one of the major strengths of this patch, which is allowing systems that don't speak the protocol to get at this information. 
 
Regarding configuration, I'd prefer a single GUC. The value can be a comma-separated list of keywords, each representing particular piece of information to be exposed.

Yes, I could see some advantages to that, although I still like the simplicity of separate boolean values. I've no strong feelings either way. Let's see if others weigh in.

Thanks for looking over this patch!

Cheers,
Greg

pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: POC: Carefully exposing information without authentication
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: Speed up COPY FROM text/CSV parsing using SIMD