Index bloat reduced in PostgreSQL v14

Re:Index bloat reduced in PostgreSQL v14 by saurik on Saturday September 11, 2021 @12:55AM (#28489523)

Is this really such a problem? I feel like you'd want pgbouncer anyway in order to mitigate connection establishment latency. Like, in my infrastructure I generally have not one but two layers of pgbouncer, one on either side of the network, so the topology of underlying network connections could be reasonably static.

[ Parent | on HN ]

Re:Index bloat reduced in PostgreSQL v14 by tomnipotent on Saturday September 11, 2021 @02:20AM (#28489803)

You'd be surprised how websites are out there running Wordpress/phpBB and managing 100+ concurrent connections with per-process pooling.

[ Parent | on HN ]

Re:Index bloat reduced in PostgreSQL v14 by castorp on Saturday September 11, 2021 @05:50AM (#28490681)

"hundreds" of concurrent connections isn't really a problem for Postgres.

Several thousands are - at least up until now. V14 will improve this substantially.

[ Parent | on HN ]

Re:Index bloat reduced in PostgreSQL v14 by tomnipotent on Saturday September 11, 2021 @03:47PM (#28495227)

Plenty of people are running on VPS or other shared hosting, with generally limited resources.

[ Parent | on HN ]

Re:Index bloat reduced in PostgreSQL v14 by pgaddict on Saturday September 11, 2021 @06:59PM (#28496890)

Well, I'd argue that's more an issue of the web application. If you're on a system with limited resources, and the webapp insists on opening hundreds of connections, assuming they're free of charge, it's a bit silly.

Anyway, this is unlikely to change anytime soon, given the Postgres connection/process model. We're continuously improving things, but each connection has some non-negligible costs (CPU, memory), so in those cases a connection pool is still a good idea.

[ Parent | on HN ]