Get the latest tech news
Tuning async IO in PostgreSQL 18
One of the significant improvements in PG18 is AIO. What are some basic tuning recommendations?
I want to share a couple suggestions on how to tune the AIO in Postgres 18, and explain some inherent (but not immediately obvious) trade-offs and limitations. Note: The benchmark (along with scripts, a lot of results and a much more detailed explanation) was originally shared in the pgsql-hackers thread about the io_method default. I saw suggestions to “use io_uring for maximum efficiency”, but the earlier benchmark clearly shows io_uring being significantly slower than worker for sequential scans.
Or read this on Hacker News
