On 2025-10-22 14:28:24 +0300, Lukas Fittl wrote:
> On Tue, Sep 9, 2025 at 10:35 PM Lukas Fittl wrote:
>
> > Attached an updated patch set that addresses the feedback, and also adds
> > the complete removal of the global pgBufferUsage variable in later patches
> > (0005-0007), to avoid counting bot
On Tue, Sep 9, 2025 at 10:35 PM Lukas Fittl wrote:
> Attached an updated patch set that addresses the feedback, and also adds
> the complete removal of the global pgBufferUsage variable in later patches
> (0005-0007), to avoid counting both the stack and the variable.
>
See attached the same pat
Hi Andres,
Thanks for the review!
Attached an updated patch set that addresses the feedback, and also adds
the complete removal of the global pgBufferUsage variable in later patches
(0005-0007), to avoid counting both the stack and the variable.
FWIW, pgWalUsage would also be nice to remove, but
Hi,
On 2025-08-31 16:57:01 -0700, Lukas Fittl wrote:
> Please find attached a patch series that introduces a new paradigm for how
> per-node WAL/buffer usage is tracked, with two primary goals: (1) reduce
> overhead of EXPLAIN ANALYZE, (2) enable future work like tracking estimated
> distinct buff
Hi,
Please find attached a patch series that introduces a new paradigm for how
per-node WAL/buffer usage is tracked, with two primary goals: (1) reduce
overhead of EXPLAIN ANALYZE, (2) enable future work like tracking estimated
distinct buffer hits [0].
Currently we utilize pgWalUsage/pgBufferUsa
