Re: Parallel Seq Scan

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bert <biertie(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel Seq Scan
Date: 2015-11-22 06:25:26
Message-ID: CAA4eK1+zZmZcndxoHDBZjukRPNc7eQ7HZepgwnALF-TqA7St3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 20, 2015 at 11:34 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, Nov 19, 2015 at 11:59 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
wrote:
> > Isn't it better to destroy the memory for readers array as that gets
> > allocated
> > even if there are no workers available for execution?
> >
> > Attached patch fixes the issue by just destroying readers array.
>
> Well, then you're making ExecGatherShutdownWorkers() not a no-op any
> more. I'll go commit a combination of your two patches.
>

Thanks!

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2015-11-22 10:20:23 Re: WIP: Make timestamptz_out less slow.
Previous Message Tom Lane 2015-11-22 05:47:35 Re: [Pgbuildfarm-members] latest buildfarm client release