Re: RFC: Allow EXPLAIN to Output Page Fault Information

From: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: andres(at)anarazel(dot)de, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org, rjuju123(at)gmail(dot)com, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: RFC: Allow EXPLAIN to Output Page Fault Information
Date: 2025-03-19 13:15:32
Message-ID: 7e182802a184ff5c9b54e575f1e3d8a2@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-03-18 08:52, Jelte Fennema-Nio wrote:
> On Mon, 10 Feb 2025 at 14:23, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
> wrote:
>> Thanks for reviewing the patch and comments!
>> Fixed issues you pointed out and attached v2 patch.
>
> This patch needs a rebase, because it's failing to compile currently.
> So I marked this as "Waiting on Author" in the commitfest app.

Thanks! I've attached an updated patch.

BTW based on your discussion, I thought this patch could not be merged
anytime soon. Does that align with your understanding?

- With bgworker-based AIO, this patch could mislead users into
underestimating the actual storage I/O load, which is undesirable.
- With io_uring-based AIO, this patch could provide meaningful values,
but it may take some time before io_uring sees widespread adoption.

--
Regards,

--
Atsushi Torikoshi
Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.

Attachment Content-Type Size
v3-0001-Add-storage-I-O-tracking-to-BUFFERS-option.patch text/x-diff 35.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2025-03-19 13:24:19 Re: PATCH: warn about, and deprecate, clear text passwords
Previous Message Melanie Plageman 2025-03-19 13:12:36 Re: Vacuuming the free space map considered harmful?