Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN

From: Tatsuya Kawata <kawatatatsuya0913(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN
Date: 2026-10-05 14:17:25
Message-ID: CAHza6qez6uSTrz9HADgkrL57iJNCx6ZAUUvQHnhgsMUUe65pww@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi David,

> I made a very small change so we only call tuplestore_rescan() when
> the parameters don't change. The call to tuplestore_clear() rewinds
> the read pointers, so there's no point in calling tuplestore_rescan()
> after tuplestore_clear().
>
> Pushed. Thanks.

Thanks for the fix and for pushing it!

Regards,
Tatsuya Kawata

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Lucas Jeffrey 2026-10-05 14:31:43 Re: Re: Re: [PATCH] Fix segmentation fault caused by reentrancy in RI_Fkey_cascade_del (ri_triggers.c)
Previous Message Richard Guo 2026-10-05 14:09:05 Re: Assert failure in try_nestloop_path()