On Thu, Nov 19, 2015 at 11:59 PM, Amit Kapila <amit.kapila16@gmail.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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company