| From: | Dave Cramer <davecramer(at)gmail(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
| Subject: | Re: Request for comment on setting binary format output per session |
| Date: | 2023-03-21 16:21:03 |
| Message-ID: | CADK3HH+fiMJ0ROyJAvBU2zuRg=21uth4MrW7NJVPNb23SYyyuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 21 Mar 2023 at 11:52, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> On Mon, 2023-03-20 at 20:18 -0400, Dave Cramer wrote:
> > For JAVA pools it's probably OK, but for pools like pgbouncer we have
> > no control of who is going to get the connection next.
>
> Can pgbouncer use different pools for different settings of
> format_binary?
>
>
My concern here is that if I can only change binary format in the startup
parameter then when I return the connection to the pool I would expect the
pool to reset all session level settings including binary format.
The next time I borrow the connection I can no longer set binary format.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-03-21 16:34:14 | Re: CREATE DATABASE ... STRATEGY WAL_LOG issues |
| Previous Message | Peter Eisentraut | 2023-03-21 16:18:53 | Re: Schema variables - new implementation for Postgres 15 |