Re: AIO v2.0 - Mailing list pgsql-hackers

From 陈宗志
Subject Re: AIO v2.0
Date
Msg-id CAGbZs7jf=YXaL3g=Xx-SRR85bQaanZi0iJh_RerspKgQQatSVg@mail.gmail.com
Whole thread Raw
In response to Re: AIO v2.0  (Andres Freund <andres@anarazel.de>)
Responses Re: AIO v2.0
List pgsql-hackers
I hope there can be a high-level design document that includes a
description, high-level architecture, and low-level design.
This way, others can also participate in reviewing the code.
For example, which paths were modified in the AIO module? Is it the
path for writing WAL logs, or the path for flushing pages, etc.?

Also, I recommend keeping this patch as small as possible.
For example, the first step could be to introduce libaio only, without
considering io_uring, as that would make it too complex.



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Avoid possible dereference null pointer (src/bin/pg_dump/pg_dump.c)
Next
From: Tom Lane
Date:
Subject: Re: Fix possible resource leaks (src/backend/replication/logical/conflict.c)