Peter Eisentraut

I think we should plan for having more than one state value. So it would be better to have a name/value listing like `SHOW CONFIG`.

In a way, this would create a behavior in pgbouncer that is stronger than what plain PostgreSQL does. Normally, a cancel request just cancels what is currently running, and there...

I can't reproduce that with a standard setup. Maybe it has something to do with the authentication setup you have. Can you play around with that a bit and see...

You also need to tell us how you attempted to connect (which command and which options), and the log entries in the postgres and pgbouncer logs from around that time.

This setup ``` [databases] test = dbname=test host=127.0.0.1 port=5432 test = auth_user=pgbouncer ``` is not correct. You have two entries for the `test` database. You need to combine those into...

It has become apparent, also through other reports, that the `[users]` section support is pretty buggy. It's good to have this reproducible report. The whole thing probably needs a deeper...

As a general rule, PgBouncer doesn't look inside packets containing SQL commands or the packets containing query results. So any scheme that relies on it recognizing certain SQL commands and...

Are you using `auth_user` or related functionality? If so, there was a bug, see #393.

I'm not sure this is the right solution. It seems unprincipled to mix in a condition based on the server's transaction status. I think the problem here is rather that...

PgBouncer isn't making up the server version anywhere, so it has to come from your backend database. So maybe get out `netstat` or similar and check where your connections are...