| From: | 陈宗志 <baotiao(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: AIO v2.0 |
| Date: | 2024-09-04 17:37:34 |
| Message-ID: | CAGbZs7jf=YXaL3g=Xx-SRR85bQaanZi0iJh_RerspKgQQatSVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2024-09-04 17:53:15 | Fix possible resource leaks (src/backend/replication/logical/conflict.c) |
| Previous Message | Nathan Bossart | 2024-09-04 17:30:01 | Re: Avoid possible dereference null pointer (src/bin/pg_dump/pg_dump.c) |