What's after postgres 18?

Key Takeaways

So, what remains? Is this the end of asynchronous IO? No. No. This is the beginning. So, one of the work they want to do is, first of all, uh all what we talked about is reads only. Postgres 18 only supports asynchronous IO for reads. So, all the background writers, the checkpoint errors, the back end stuff that writes, none of that that stuff is still sync. And that Don't quote me on that. Quote Andreas. This is from the talk 2 months ago he did in 2025 August. Okay? Yeah, so writes is not supported for asynchronous yet. So, you can only do reads. Uh I think reads are more important because once you write, you don't really do much, right? You already did the CPU work. Right? But I suppose you can do more stuff, CPU stuff, as you're writing. So, you can move and do more stuff. But yeah, I think writes will definitely benefit. Yeah, so that writes, no writes yet. Right? So, that that work is being worked on in the future. They're going to enable start enabling it for all the other, you know, processes that does writes. Yeah, so they're working on a enhancing the the worker mode, essentially, to to be more flexible, right? I think today the way they have the worker mode is like the default is three. And then it doesn't really You can change it and restart the Postgres instance to to pick it up, right? But it's not flexible. You cannot just change it in runtime. Plus, uh even if you if you set it to a large number, let's say 50, uh it spins up those 50 at the start. And then those 50 will remain there whether they are used or not. So, they want to make it like elastic a little bit. So, that uh the Postgres instances the those workers will spin down when they are not needed. And they will spin back up when they are. Just to save on memory and and just over unnecessary overhead, right? So, that they're working on that, making the worker better. And um the worker for Windows support, so uh at least for IO Uring for Windows, which is IOCP. So, to support IOCP for Windows,