Peter Eisentraut

Something caused the connection to the PostgreSQL server to be interrupted. You'll have to investigate that yourself. Check the PostgreSQL logs. Maybe the server process was killed.

Please provide a reproducible test case with full configuration, version numbers, exact sequence of commands, and all outputs.

> psql -h localhost -p 6432 -U user1 mydbname > > psql -w -h localhost -p 6432 -U user1 mydbname > psql -h localhost -p 6432 -U user1 server_nr #...

> Upon further testing, I have found the following: > > * Comments interrupt and/or confuse the parsing of `userlist.txt` `user`/`password` combinations. > * The order of duplicate users is...

I cannot reproduce this. Can you send your complete setup, `pgbouncer.ini`, `userlist.txt`, `pg_authid` contents, etc.?

The problem is that in PgBouncer internally, users with the same name can exist multiple times in different contexts: - globally (from `auth_file`) - PAM user - attached to a...

Please show your `pgbouncer.ini` configuration file, and also the exact commands that you enter.

Well, we are the PgBouncer development team. We don't publish any Docker stuff or know what it does. So if you want help from us, you will need to peek...

Are those spaces in `host = dev8_db` really there?

You could start pgbouncer with a higher `verbose` setting (like `verbose=2`). That will print additional information about what connections it is opening.