Asynchronous I/O

In Postgres, right? Like I think, and also if you look at the evolution that Postgres has had over the past few years, it is more than proprietary forks.

If you look at async IO, big feature, right? A logical replication evolution has been crazy.

I know that like there is also some work going on active, active, et cetera, right? So overall, I think it's a combination of trust, right? Like it's battle tested because I think we need to be really careful about building databases with AI, right? Like, by the way, like Wallshadow AI was involved, right? And AI helped a lot in like building Wallshadow.

But we are like, we embrace it because we also are experts like Philip, right? Eight years worked with like Postgres, right? Knows

Yeah.

So that's the major difference from Async.io and Tonio, right? When you spawn stuff, that thing happens in parallel.

So by default, Tonio starts with the number of threads equal to the number of your CPUs.

The blocking...