From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Shaik Mohammad Mujeeb <mujeeb(dot)sk(at)zohocorp(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, mujeebskdev <mujeeb(dot)sk(dot)dev(at)gmail(dot)com> |
Subject: | Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer |
Date: | 2025-05-27 22:22:27 |
Message-ID: | CAKFQuwYHTOyN435-ARCNRJpCy0aDi2isvy-3W1r20mWq8WFu+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 27, 2025 at 3:08 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > psql has zero awareness of pgbouncer or any other non-PostgreSQL server
> you
> > might be able to point it to and establish a successful connection. The
> > lack of a warning previously is probably more incorrect than its presence
> > now.
>
> Yeah. I'd say the fundamental problem is that pgbouncer is abusing
> the server_version parameter, which will break plenty of things
> besides psql --- pg_dump for instance
They proxy over the real server information during actual bouncer work -
it's just their local administrative database connection - one that isn't
proxied - that is at issue here.
> Anyway, I'm minus quite a lot on silencing this warning, because
> it is telling you about real problems you are likely to hit.
>
>
How about the false-negative that was happening for years when this warning
didn't appear even though you were connected to pgbouncer and not
PostgreSQL?
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-05-27 22:34:15 | Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer |
Previous Message | Tom Lane | 2025-05-27 22:08:12 | Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer |