Nikita Kazmin

AFAIK we don't use SearchPath for resolving, we just pass it to PG.

So, a new connection string param `PoolLifetime`, which dictates for how long a pool will be alive?

Sure, why not.

> Maybe just clear the pool if there are no connections? We already have maximum connection lifetime which controls how long it can survive and max idle lifetime too. Good...

@terminalairlines are you by any chance connect via a secure connection? If so, could you check if by adding `CancellationTimeout=-1` to the connection string helps?

This definitely looks like a race condition, although I can't say yet what exactly makes it manifest (going to run a few test today). In the meantime, the best way...

@joecarr okay, from the logs I can say that: 1. The cancellation itself is most likely not a culprit (we send it whenever the timeout is reached, in your case,...

@joecarr Very sorry for the wait, was busy with personal stuff. Is it possible for you to test a few things: 1. Try to connect to PgBouncer without SSL 2....

Hello everyone. There has been found a possible reason for this error. You can find more info here: https://github.com/npgsql/npgsql/issues/4305#issuecomment-1086728515.

@ZenwalkerD you should pass `CancellationTimeout`, and not `ConnectionTimeOut`. Are you using Npgsql with .NET Framework and SSL?