to be consider:
disabling DB-side cursors; they should be disabled with transaction based pgbouncer pooling anyhow and they will break on reconnection
this fixed OperationError that happens sometimes with pgbouncer (especially if it has some proxy in front of it).
Fixed issues when working with Vultr postgresql db.
to be consider: disabling DB-side cursors; they should be disabled with transaction based pgbouncer pooling anyhow and they will break on reconnection
this fixed OperationError that happens sometimes with pgbouncer (especially if it has some proxy in front of it). Fixed issues when working with Vultr postgresql db.