Re: [PATCH] Add memory/disk usage for Function Scan nodes in EXPLAIN

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tatsuya Kawata <kawatatatsuya0913(at)gmail(dot)com>
Cc: Yash Jadhav <yash(dot)jadhav8008(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add memory/disk usage for Function Scan nodes in EXPLAIN
Date: 2026-10-23 08:24:37
Message-ID: CAApHDvr_obD-BdfyJYBPexoigg5McPbmDtDS8phXg5cTvren1w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 16 Oct 2026 at 04:01, Tatsuya Kawata
<kawatatatsuya0913(at)gmail(dot)com> wrote:
> Thanks for pointing that out! That makes sense. Attached is v5.

I looked at v5. Can we not switch back to how you had it in v2 by
moving the FunctionScanPerFuncState into execnodes.h and using that
directly in explain.c? It's the FunctionNext() changes that I'm not
keen on. I feel that's adding too much code to a function that
executes on every row. I quickly put that together in the attached,
which applies on top of v5. It seems to pass the tests. I didn't look
further than that, so please check.

David

Attachment Content-Type Size
nocfbot-fixes.diff.txt text/plain 10.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2026-10-23 08:46:48 Re: [DEPARSE] EXPLAIN prints another ModifyTable's RETURNING aliases in a SubPlan
Previous Message David Geier 2026-10-23 08:18:31 Re: Use correct collation in pg_trgm