FRESH

Hacker News

Home

Why we built yet another Postgres connection pooler

257 points by levkk

by AdieuToLogic

0 subcomment

The fact that PgDog supports prepared statements[0] is a compelling feature in and of itself. This was a limitation of older versions of pgpool-II[1] thus disqualifying it in efforts where it otherwise could have been beneficial.
0 - https://docs.pgdog.dev/features/connection-pooler/prepared-s...
1 - https://www.pgpool.net/docs/4.7/en/html/

by 27183

2 subcomments

It's awesome to see AGPL instead of the horrible BSL variants that have been going around.

by abrookewood

0 subcomment

Quick note to say that the article describing WHY you are different and why it matters was very well written. Congrats on the launch!

by petters

6 subcomments

> Since connection poolers reuse connections between clients, the connection state of one client “leaks” into the connection state of another.
Wow this is very bad. This actually happens in typical Postgres setups?

by dwedge

0 subcomment

The SET implementation reads like a cleaner version of how ProxySQL does the same thing, which is nice to see

by ransom1538

4 subcomments

Can someone explain it to me like I am 5. Why did postgres win vs mysql? I don't know many companies at scale that use postgres. Slack, youtube, etc all use a mysql based sharding system https://vitess.io/. I thought the war was lost for postgres, but it seems to keep going. License issues? (Disclosure, I manage 'a few' mysql vms).

by rastignack

0 subcomment

And why it should be done upstream with a thread pool model and an internal scheduler as MS SQL server does.

by rubenvanwyk

2 subcomments

What really interests me most is the sharding and the possibility of using this for multitenancy - is the hooks / plugin architecture sufficient so you can run a small sidecar to add shards or tenants to the TOML file dynamically? Would be a game changer.

by kardianos

1 subcomments

What posgresql needs is a new wire format. (pgwire4)
I've been slopping together a POC to probe the edges of what can be done as just an extension. So far I have a framed protocol with inline cancellation, named parameters, out-of-query text language selector, ad-hoc pg/PLSQL execution with cache (no need for prepare), multiple result sets, streaming large results, and more flexible bulk upload.
In other words, with this extension you can query:
``` select * from T1; select * from T2; ```
And return them both in PG/PLSQL or straight SQL.
The existing pgwire3 protocol is one of the worst things to work with in postgresql.

by inigyou

1 subcomments

Doesn't this NOTIFY performance fix mean that it isn't transactional any more?

by jauntywundrkind

1 subcomments

Clickhouse also just put out a fun article on scaling pgbouncer too, talking about scaling out so_reuseport while not having to shard so harshly (a major limitation pgdog here is addressing via rewrite), https://clickhouse.com/blog/pgbouncer-clickhouse-managed-pos... https://news.ycombinator.com/item?id=48814152

by khurs

2 subcomments

Any plans to add Query Caching for Selects?
as per:
https://www.pgpool.net/docs/latest/en/html/runtime-in-memory...

by mctwo

0 subcomment

This is a really neat project, congrats on the launch!

by icevl

0 subcomment

Postgres features still "just work" behind the pooler.

by babayega2

0 subcomment

Is there a pooler handling schema switching in PostgreSQL? like something in front of django-tenant ?

by mmakeev

2 subcomments

we moved our django app behind pgbouncer transaction pooling a few days ago and the surprise wasn't SET so much as queryset.iterator(). it relies on server side cursors, which don't survive being pooled, so we had to disable it everywhere and let it fall back to client side. also had to move statement_timeout out of the app's connection options into the pooler's own connect query, since libpq startup params just get silently ignored behind it.

by Aejkatappaja

0 subcomment

[flagged]

by s8kur

0 subcomment

[flagged]

by Technical_Plant

0 subcomment

[flagged]

by danielsmori

0 subcomment

[flagged]

by huflungdung

0 subcomment

[dead]

by fernando-ram

0 subcomment

[flagged]