| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Request for comment on setting binary format output per session |
| Date: | 2023-03-27 00:39:28 |
| Message-ID: | CADK3HH+qAAkgcYYS99CfAMF+62QY3oQ_qxSF2h5+p0VJiAZgZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Cramer
On Sun, 26 Mar 2023 at 18:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Cramer <davecramer(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kirk Wolak | 2023-03-27 01:12:35 | Documentation Not Compiling (http://docbook... not https:.//...) |
| Previous Message | Andrey Borodin | 2023-03-26 22:17:02 | Re: Amcheck verification of GiST and GIN |