Hacker News new | past | comments | ask | show | jobs | submit login

Does anyone know when the update allowing more concurrent connections is dropping, so we can stop using pgbouncer?



I recently read a great article exploring what would change if they were to switch from processes to threads for each connection. Running a connection pooler didn't seem so bad to me after reading it. https://medium.com/@tusharmalhotra_81114/why-postgresql-choo...


That'll likely need conversion from process per connection, so not any time soon


FWIW, there actually are some ongoing efforts towards that - including several preparatory changes in PG 18. Still lots more work, but we are working towards it.

https://wiki.postgresql.org/wiki/Multithreading


Do you know, how well pgbouncer works with prepared statement nowadays? We slowly migrating our clusters to pg16/new bouncer and feel unsure on stability and reliability of prepared statements support




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: