Re: Report buffer access strategies in EXPLAIN

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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 08:10:21
Message-ID: awAAbRC6qcS2r1fw@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Fri, Nov 20, 2026 at 04:49:48PM +0900, Michael Paquier wrote:
> 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,

Thanks for confirming!
>
> 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.

Yeah you already mentioned that up-thread and I replied "I’m not sure as the
pg_stat_io wording is a pre existing issue that can be backpatched, while I think
that 0002 adds documentation on master". Did you miss that reply or are you not
convinced?

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Geier 2026-11-20 08:14:30 Re: Use local buffer for packed numerics
Previous Message Bertrand Drouvot 2026-11-20 08:04:19 Re: pg_restore fails on extracted tar archives with large objects