Re: Request for comment on setting binary format output per session - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: Request for comment on setting binary format output per session
Date
Msg-id CADK3HHLXnkcxWGGkQTWFnLqDr=Rn4XvkUUzpN6b2gs_pfEHB1A@mail.gmail.com
Whole thread Raw
In response to Re: Request for comment on setting binary format output per session  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Request for comment on setting binary format output per session  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


On Tue, 10 Oct 2023 at 10:25, Robert Haas <robertmhaas@gmail.com> wrote:
On Mon, Oct 9, 2023 at 4:25 PM Jeff Davis <pgsql@j-davis.com> wrote:
> Another thing to consider is that using a GUC for binary formats is a
> protocol change in a way that client_encoding is not. The existing
> documentation for the protocol already specifies when binary formats
> will be used, and a GUC would change that behavior. We absolutely would
> need to update the documentation, and clients (like psql) really should
> be updated.

I think the idea of using a new parameterFormat value is a good one.
Let 0 and 1 continue to mean what they mean, and let clients opt in to
the new mechanism if they're aware of it.

Correct me if I am wrong, but the client has to request this. So I'm not sure how we would be surprised ?

Dave

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Request for comment on setting binary format output per session
Next
From: Robert Haas
Date:
Subject: Re: Request for comment on setting binary format output per session