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 CADK3HH+qAAkgcYYS99CfAMF+62QY3oQ_qxSF2h5+p0VJiAZgZA@mail.gmail.com
Whole thread Raw
In response to Re: Request for comment on setting binary format output per session  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Request for comment on setting binary format output per session  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Dave Cramer


On Sun, 26 Mar 2023 at 18:12, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Dave Cramer <davecramer@gmail.com> writes:
> Well I was presuming that they would just pass the parameter on. If they
> didn't then binary_format won't work with them. In the case that they do
> pass it on, then DISCARD_ALL will reset it and future borrows of the
> connection will have no way to set it again; effectively making this a one
> time setting.

I would not expect DISCARD ALL to reset a session-level property.

Well if we can't reset it with DISCARD ALL how would that work with pgbouncer, or any pool for that matter since it doesn't know which client asked for which (if any) OID's to be binary. 

Dave

pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: Amcheck verification of GiST and GIN
Next
From: Kirk Wolak
Date:
Subject: Documentation Not Compiling (http://docbook... not https:.//...)