Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer

From: Julien Rouhaud <rjuju123(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>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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-28 00:03:09
Message-ID: CAOBaU_Z2-hjvPDkZcqb4mBvP79oB5MOtHF=ycxnT613F3ZScbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 28 May 2025, 07:21 Tom Lane, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Shaik Mohammad Mujeeb <mujeeb(dot)sk(at)zohocorp(dot)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.

>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-05-28 00:40:19 Re: Fix slot synchronization with two_phase decoding enabled
Previous Message Sami Imseih 2025-05-27 23:43:01 Re: queryId constant squashing does not support prepared statements