Waiting for Postgres 18: Accelerating Disk Reads with Asynchronous I/O

Re:Waiting for Postgres 18: Accelerating Disk Reads with Asy... by pseudopersonal on Wednesday May 07, 2025 @12:16PM (#43917563)

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

[ Parent | on HN ]

Re:Waiting for Postgres 18: Accelerating Disk Reads with Asy... by __s on Wednesday May 07, 2025 @12:38PM (#43917829)

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

[ Parent | on HN ]

Re:Waiting for Postgres 18: Accelerating Disk Reads with Asy... by anarazel on Thursday May 08, 2025 @09:48AM (#43926085)

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

[ Parent | on HN ]

Re:Waiting for Postgres 18: Accelerating Disk Reads with Asy... by hoherd on Thursday May 08, 2025 @08:03AM (#43925317)

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...

[ Parent | on HN ]

Re:Waiting for Postgres 18: Accelerating Disk Reads with Asy... by CoolCold on Thursday May 08, 2025 @01:16PM (#43928551)

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

[ Parent | on HN ]