Re: RFC: Allow EXPLAIN to Output Page Fault Information

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Atsushi Torikoshi <torikoshia(dot)tech(at)gmail(dot)com>
Cc: vellaipandiyan sm <vellaipandiyan(dot)sm(at)gmail(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: RFC: Allow EXPLAIN to Output Page Fault Information
Date: 2026-05-24 09:50:00
Message-ID: CAGECzQSOrmOTSyVHi1tkx9QDg9_PkVJudtdTH0B7ovHeZXtFLQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 22 May 2026 at 18:07, Atsushi Torikoshi
<torikoshia(dot)tech(at)gmail(dot)com> wrote:
> Updated the patch to clarify that the reported values include not only
> the backend process executing the query, but also any parallel query
> worker processes involved in the query.

For PG19 Tomas added an IO option to EXPLAIN. I think it would be
better to have the Storage IO tracking be enabled by the IO option,
rather than the BUFFERS option.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan Gonzalez V. 2026-05-24 10:10:05 Re: splitting pg_resetwal output strings
Previous Message Jonathan Gonzalez V. 2026-05-24 09:48:13 Re: splitting pg_resetwal output strings