Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer
Date
Msg-id CAOBaU_Z2-hjvPDkZcqb4mBvP79oB5MOtHF=ycxnT613F3ZScbA@mail.gmail.com
Whole thread Raw
In response to Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer  (Shaik Mohammad Mujeeb <mujeeb.sk@zohocorp.com>)
List pgsql-hackers
On Wed, 28 May 2025, 07:21 Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Shaik Mohammad Mujeeb <mujeeb.sk@zohocorp.com> writes:
> So, I feel that if we can reliably detect when the backend is a non-PostgreSQL server, it might be better to adjust the warning accordingly, rather than relying on a client-server version comparison in such cases.

The entire point of having a wire protocol is that you can't/don't
need to detect that.  The short answer here is that this is
pgbouncer's bug and you should be nagging them to change, not us.

maybe I'm missing something but it seems like it's behaving as expected. pgbouncer advertises a version that both seems to be understood by the protocol and is incompatible with any real postgres version.  since such connection only allows plain SHOW statement, the warning about some psql features seems perfectly accurate, if not wildly an understatement as literally no psql feature will work. 
 

pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: Review/Pull Request: Adding new CRC32C implementation for IBM S390X
Next
From: Masahiko Sawada
Date:
Subject: Re: Fix slot synchronization with two_phase decoding enabled