News for hackers. Stuff that matters.

A comment on Tips for a Healthier Postgres Database.

Re:Tips for a Healthier Postgres Database by cloudyglider on Saturday January 08, 2022 @11:49PM (#29860250)
> On versions prior to Postgres 14, connections consumed extra overhead leaving idle connections as wasted space.

Does this mean PGbouncer is unnecessary for postgres > v14?

[ Parent | on HN ]
Re:Tips for a Healthier Postgres Database by osigurdson on Sunday January 09, 2022 @02:01AM (#29860962)
It was improved in 14 but may not eliminate the need for pgbouncer depending on the use case.

https://pganalyze.com/blog/postgres-14-performance-monitorin...

[ Parent | on HN ]
Re:Tips for a Healthier Postgres Database by andruby on Sunday January 09, 2022 @01:34AM (#29860860)
There is still value in constraining the maximum number of concurrent queries. That’s PgBouncers main task.
[ Parent | on HN ]
Re:Tips for a Healthier Postgres Database by jeltz on Sunday January 09, 2022 @07:39AM (#29862725)
It is less necessary but it could still be worth running it since there is still a bit if overhead plus PgBouncer can be used to when doing failovers.
[ Parent | on HN ]