Re: Material node can report incorrect "Maximum Storage" in EXPLAIN

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Material node can report incorrect "Maximum Storage" in EXPLAIN
Date: 2026-10-05 00:46:26
Message-ID: CAApHDvqwZy4wBQtWvS5i=BAd=7n1+OQm-JrTE7mpCJZGv44ntg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 1 Oct 2026 at 19:49, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> The patch looks good to me.
>
> > The misreporting of the storage likely isn't a big deal. I suspect
> > rescans of Material nodes are not massively common, so maybe it's not
> > worth backpatching a fix.
>
> I have no evidence but I feel same as you (rescans of Material nodes
> are not massively common). Probably it's not worth backpatching. If we
> need backpatching, we could do it later.

Thanks for the review. I went with no backpatch for now.

Pushed after addressing the things mentioned by Kawata-san.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-05 01:19:22 Re: doc: Document Linux cgroup memory limits
Previous Message Joao Detomini 2026-10-05 00:38:50 Re: doc: Document Linux cgroup memory limits