On Thu, Nov 19, 2015 at 9:29 PM, Robert Haas <robertmh...@gmail.com> wrote: > > On Wed, Nov 18, 2015 at 10:41 PM, Amit Kapila <amit.kapil...@gmail.com> wrote: > > I think whats going on here is that when any of the session doesn't > > get any workers, we shutdown the Gather node which internally destroys > > the dynamic shared memory segment as well. However the same is > > needed as per current design for doing scan by master backend as > > well. So I think the fix would be to just do shutdown of workers which > > actually won't do anything in this scenario. > > It seems silly to call ExecGatherShutdownWorkers() here when that's > going to be a no-op. I think we should just remove that line and the > if statement before it altogether and replace it with a comment > explaining why we can't nuke the DSM at this stage. >
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. With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
fix_early_dsm_destroy_v2.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
