Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN - Mailing list pgsql-hackers

From Tatsuya Kawata
Subject Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN
Date
Msg-id CAHza6qez6uSTrz9HADgkrL57iJNCx6ZAUUvQHnhgsMUUe65pww@mail.gmail.com
Whole thread
In response to Re: Table Function Scan can report incorrect "Maximum Storage" in EXPLAIN  (David Rowley <dgrowleyml@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: Assert failure in try_nestloop_path()
Next
From: Lucas Jeffrey
Date:
Subject: Re: Re: Re: [PATCH] Fix segmentation fault caused by reentrancy in RI_Fkey_cascade_del (ri_triggers.c)