3 ms·

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

• __s 1y ago
  That'll likely need conversion from process per connection, so not any time soon
  • anarazel 1y ago
    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 https://wiki.postgresql.org/wiki/Multithreading
• hoherd 1y ago
  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-chooses-processes-over-threads-and-why-it-matters-9011a98e1d84 https://medium.com/@tusharmalhotra_81114/why-postgresql-choo...
• CoolCold 1y ago
  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