On Tue, Nov 03, 2026 at 11:49:03PM -0800, Lukas Fittl wrote: > I think ultimately our problem is that we need some way to "attach" > the worker WAL/buffer activity to the right executor node (i.e. the > one that caused a nested statement to be called that had worker > activity), and that node then needs to be able to accumulate that > activity upwards to parent nodes, potentially other parent statements, > and the query-level instrumentation, all without affecting the global > top value like it does today.
Could it help if the instrument structure had a secondary set of fields for the worker data, then, when you want to pass its information across the stack? Or would that impact the performance of InstrStopNode() as well? For example, for pgWalUsage just a pgWalUsageWorkers? (If I'm missing something and I am not in line with your previous arguments, sorry, it's been a long day and it's the end of the so-said day..) -- Michael
signature.asc
Description: PGP signature
