From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
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:08:12 |
Message-ID: | 1350175.1748383692@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"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, and just about any other
application that needs to adjust its queries to suit different
Postgres server versions. If they feel a need to advertise
pgbouncer's version there, it wouldn't be that hard to make
server_version read out as something like "17.5 (pgbouncer XX.YY)",
which would not confuse libpq/psql (cf. parsing code in
pqSaveParameterStatus). But apparently they didn't do that.
Anyway, I'm minus quite a lot on silencing this warning, because
it is telling you about real problems you are likely to hit.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2025-05-27 22:22:27 | Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer |
Previous Message | Sami Imseih | 2025-05-27 22:05:39 | Re: queryId constant squashing does not support prepared statements |