4 ms·
There is definitely a demand for it, there are really three problems that exist with connections in Postgres. 1. The initial time to establish a connection is
by craigkerstiens 7y ago
There is definitely a demand for it, there are really three problems that exist with connections in Postgres.
1. The initial time to establish a connection is higher than would be ideal
2. Each connection, even an idle one, has an overhead of roughly 10 MB. For idle connections this is pretty much wasted space and most application frameworks grab a pool of connections accumulating quite a few idle connections.
3. The max number of connections you can push the system to is somewhere in hundreds to low thousand. Yes, it is possible to push PG further but it is not trivial.
But, the sad reality is it isn't a trivial quick fix. There are a lot of foundational issues with connection that have to be fixed. There are some folks and efforts in the community working towards this, and in my opinion it is the single biggest improvement that could happen in Postgres over the next 2-3 years, so hopefully it will improve directly in core over time.
- AaronFriel 7y agoCan you remove the leading spaces so that this text is readable without scrolling? Even on my 4k monitor I must scroll to read each line.
- majewsky 7y agoWithout broken formatting: > 1. The initial time to establish a connection is higher than would be ideal > 2. Each connection, even an idle one, has an overhead of roughly 10 MB. For idle connections this is pretty much wasted space and most application frameworks grab a pool of connections accumulating quite a few idle connections. > 3. The max number of connections you can push the system to is somewhere in hundreds to low thousand. Yes, it is possible to push PG further but it is not trivial.