Peter Eisentraut

I'm thinking maybe it's running in some kind of restricted environment where the network functionality is restricted. Otherwise I can't explain why you can't even create sockets. (Note that this...

It's an interesting feature. I will look at it.

I have studied some approaches to prepared statement support in pgbouncer recently. I don't think I want to tell clients "I'm PgBouncer" or "I'm in transaction pooling mode" and have...

> I'm sorry, I'm not familiar with JDBC. Do you mean taking a `prepareThreshold` connection parameter to disable preparing in case the client knows it is connecting to PgBouncer? Yes,...

> Just thinking out freely, this may be wrong, but..: > what if there was a pam module "pam-postgresql" > which would allow pam to manage it's authentication against a...

I've studied this a bit today. One major issue that I have identified is how authenticating the same user sometimes via PAM and sometimes not works. Internally, PgBouncer tracks PAM...

The error message discrepancy was fixed in 6a9cffe2.

As was explained, `server_lifetime` doesn't mean that the server connection is killed immediately when the lifetime is reached. It just means that when the server is freed, then it is...

> The address S-0xc51588 is first closed because of the server_lifetime parameter, there is a new login attempt and the same address is reused to open the new connection to...

Please provide a self-contained test configuration for this.