Re: RFC: Allow EXPLAIN to Output Page Fault Information

torikoshia <torikoshia@oss.nttdata.com>

From: torikoshia <torikoshia@oss.nttdata.com>

To: Jelte Fennema-Nio <postgres@jeltef.nl>

Cc: andres@anarazel.de, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org, rjuju123@gmail.com, Bruce Momjian <bruce@momjian.us>

Date: 2025-03-19T13:15:32Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Avoid leaking system path from pg_available_extensions
- db5ed03217b9 19 (unreleased) cited
Enable BUFFERS with EXPLAIN ANALYZE by default
- c2a4078ebad7 18.0 cited

Attachments

v3-0001-Add-storage-I-O-tracking-to-BUFFERS-option.patch (text/x-diff) patch v3-0001

Hi,

On 2025-03-18 08:52, Jelte Fennema-Nio wrote:
> On Mon, 10 Feb 2025 at 14:23, torikoshia <torikoshia@oss.nttdata.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.