Re: [HACKERS] [POC] Faster processing at Gather node

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] [POC] Faster processing at Gather node
Date: 2017-11-30 02:03:50
Message-ID: CAB7nPqTsymCHtBjx_F-efYLFyXmA2VJrfmrpokeSh-SJcgVxVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 26, 2017 at 5:15 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-11-30 02:05:16 Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Previous Message Michael Paquier 2017-11-30 02:02:06 Re: [HACKERS] Surjective functional indexes