Re: Report buffer access strategies in EXPLAIN

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>, Lukas Fittl <lukas(at)fittl(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Report buffer access strategies in EXPLAIN
Date: 2026-11-20 07:49:48
Message-ID: av_7nM04wFg0LEco@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 19, 2026 at 11:59:59AM +0000, Bertrand Drouvot wrote:
> PFA v6, mandatory mechanical rebase due to 556c025db96.

Hmm. I like what I am reading in 0001 and 0002, and I'd be tempted to
apply these two.

For 0003, adding the strategy name, which is the same name as the
state stored in pg_stat_io, feels like unnecessary duplicated
information. The first paragraph providing a link to the glossary
that explains the strategy names would be sufficient, IMO, so I'd just
keep the first paragraph update, merge it into 0002.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2026-11-20 07:54:58 Re: Table AM callback for logical decoding support (REPACK CONCURRENTLY)
Previous Message Heikki Linnakangas 2026-11-20 07:49:19 Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS