Re: Stack-based tracking of per-node WAL/buffer usage - Mailing list pgsql-hackers

On Wed, Mar 25, 2026 at 5:41 PM Lukas Fittl <lukas@fittl.com> wrote:
> On Wed, Mar 25, 2026 at 3:47 AM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> > This patch could use an overview README file, I'm struggling to
> > understand how the this all works. Here's my understanding so far,
> > please correct me if I'm wrong:
>
> Sure, happy to put this together - I wonder where would place that
> best - probably src/backend/executor/README.instrument ?

I've gone ahead and added that in
src/backend/executor/README.instrument for now, trying to take some of
your prior email as inspiration, whilst not fully committing to
describing it as a tree - but happy to revise that if we feel its
important for clarity.

See attached v11, rebased after the pgBufferUsage calls were moved in
df09452c3209, and also fixing the issues that Zsolt noted in a
previous email reviewing v10.

I've also moved pg_session_buffer_usage to be a
test_session_buffer_usage module instead, since its not intended as a
user accessible module. If we wanted to commit that (not sure if its
worth the cycles), we could potentially merge it with the 0004 commit
that expands the main regression tests.

Thanks,
Lukas

--
Lukas Fittl