On Tue, May 27, 2025, at 3:41 PM, Shaik Mohammad Mujeeb wrote:
In my case, pset.sversion ends up being 12001 (due to PgBouncer v1.20.1), and since that’s less than 90200, the warning gets triggered, which feels misleading. But I was wondering - does it really make sense to compare PgBouncer’s version in this context using the same logic as PostgreSQL server versions?
Yes. Because that comparison is for any server that psql connects to.
Is this an expected behaviour, or would it make sense to handle Pgbouncer differently in this check?
See similar issue [1]. The error is not totally misleading. As I stated in [1],
pgbouncer is a special database. IMO it makes sense to report that some
features don't work because that's true; backslash commands don't work.
Regarding the server version, PgBouncer is a server for the client. Nothing
wrong to report it too. If you don't want to see this message use --quiet
option. In my experience, this special database is frequently used by scripts
to obtain PgBouncer statistics. These scripts generally use --quiet option
anyway. I don't think we need an extra option just to suppress this warning.
