Re: Material node can report incorrect "Maximum Storage" in EXPLAIN - Mailing list pgsql-hackers

From David Rowley
Subject Re: Material node can report incorrect "Maximum Storage" in EXPLAIN
Date
Msg-id CAApHDvqwZy4wBQtWvS5i=BAd=7n1+OQm-JrTE7mpCJZGv44ntg@mail.gmail.com
Whole thread
In response to Re: Material node can report incorrect "Maximum Storage" in EXPLAIN  (Tatsuo Ishii <ishii@postgresql.org>)
List pgsql-hackers
On Thu, 1 Oct 2026 at 19:49, Tatsuo Ishii <ishii@postgresql.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



pgsql-hackers by date:

Previous
From: Joao Detomini
Date:
Subject: Re: doc: Document Linux cgroup memory limits
Next
From: Manu
Date:
Subject: Re: doc: Document Linux cgroup memory limits