Jelte Fennema-Nio
Jelte Fennema-Nio
Okay, re-opening to see if we should change our HBA logic and have ipv4 rules match these addresses.
You need to add `auth_user` to your `pgbouncer.ini.
> > You need to add `auth_user` to your `pgbouncer.ini. > > @JelteF You mean now I need to add `auth_user` like this or something ? Yes
Oh I now see you have set `auth_user` in the database line. That should work as well. Do you have logs from Postgres and PgBouncer during this time.
I considered this case to be quite unlikely to actually happen on purpose in https://github.com/pgbouncer/pgbouncer/pull/908 (see pr description too). So I thought throwing a error to indicate the user error...
Hmm, I didn't realise that was valid syntax. If you change it to the following that should solve your immediate problem. array('-c client_encoding=utf8', '-c standard_conforming_strings=on'); But indeed postgres allows the...
To be clear this format wasn't the one I considered unlikely to be used, it was just one I did not know existed. The ones I intended to explicitly disallow,...
I created #1064 to fix this issue btw. If you could confirm that that fixes your issue that would be helpful.
That indeed sounds useful. Instead of `default_pool_size` it would be best if we call it `pool_size` though (just like it's called in the `[databases]` section. Feel free to open a...
Hmm, that indeed sounds annoying to debug. We should log the error provided by postgres instead of saying only "error response from auth_query". If you want to contribute a PR...