How to Manage Connections Efficiently in Postgres, or Any Database

Re:How to Manage Connections Efficiently in Postgres, or Any... by dijit on Monday October 15, 2018 @05:58PM (#18224203)

PgBouncer doesn’t save you from a lot of the actual pain when dealing with connections. And that’s prepared statements, you can’t pool prepared statements so high volume transactional databases need a lot of connections.

Including pgbouncer in the base package would just mask the issue because pgbouncer saves you (mainly) from the short lived connection.

[ Parent | on HN ]

Re:How to Manage Connections Efficiently in Postgres, or Any... by EB66 on Tuesday October 16, 2018 @01:03AM (#18226674)

> PgBouncer doesn’t save you from a lot of the actual pain when dealing with connections. And that’s prepared statements, you can’t pool prepared statements

Prepared statements work fine with PgBouncer when you have session pooling enabled (as opposed to transaction pooling).

It may not save you from all the pain of dealing with connections, but PgBouncer definitely helps a lot when you're working with remote Postgres servers and high latency (i.e., > 10ms). Mitigating the delay and cost of connection initiation is pretty huge.

[ Parent | on HN ]

Re:How to Manage Connections Efficiently in Postgres, or Any... by dijit on Wednesday October 17, 2018 @07:15AM (#18237950)

Only if your code is not connection pooling itself.

In my case that is true, but for a php webapp (for example) it is a lot less true.

[ Parent | on HN ]