On Sun, Nov 26, 2017 at 5:15 PM, Amit Kapila <amit.kapil...@gmail.com> wrote: > Yeah and I think something like that can happen after your patch > because now the memory for tuples returned via TupleQueueReaderNext > will be allocated in ExecutorState and that can last for long. I > think it is better to free memory, but we can leave it as well if you > don't feel it important. In any case, I have written a patch, see if > you think it makes sense.
OK. I can see some fresh and unreviewed patches so moved to next CF. -- Michael
