"David G. Johnston" <david.g.johnston@gmail.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?
