CONNECTION_CLOSED with PgBouncer

[deman4ik]

Sometimes I have CONNECTION_CLOSED errors while using PgBouncer in transaction mode.

Any suggestions how I can may be tweak some connection parameters to prevent those kind of errors?

Direct connection to Pg seems working fine.

[porsager]

Could you give postgres@beta a shot?

…

On 9 Jul 2020, at 16:21, Dmitriy Shatalov ***@***.***> wrote:  Sometimes I have CONNECTION_CLOSED errors while using PgBouncer in transaction mode. Any suggestions how I can may be tweak some connection parameters to prevent those kind of errors? Direct connection to Pg seems working fine. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[deman4ik]

@porsager It turns out I’m already using it on dev environment. So this problem occurs in beta version.

[porsager]

Ahha.. It seems that if you run in transaction mode Protocol-level prepared plans which Postgres.js does automatically for you, is not allowed with PgBouncer. It says in the footnote that

It is possible to add support for that into PgBouncer.

But it doesn't lead to anywhere, so maybe it's something they're looking at for the future?

I would say this is another good reason to add an option to disable the automatic prepared statements in Postgres.js, which was also mentioned in another issue.

Edit: I found pgbouncer/pgbouncer#242 and pgbouncer/pgbouncer#467 which talks about supporting it in PgBouncer.

[mrl5]

worth noting that since PgBouncer >=1.21.0 protocol-level named prepared statements are supported. Additional ref: https://www.pgbouncer.org/config.html#max_prepared_statements

max_prepared_statements

When this is set to a non-zero value PgBouncer tracks protocol-level named prepared statements related commands sent by the client in transaction and statement pooling mode