On Thu, Sep 17, 2015 at 6:29 AM, Haribabu Kommi <kommi.harib...@gmail.com> wrote: > > On Thu, Sep 17, 2015 at 6:10 AM, Robert Haas <robertmh...@gmail.com> wrote: > > On Thu, Sep 10, 2015 at 12:12 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > >>> 2. I think it's probably a good idea - at least for now, and maybe > >>> forever - to avoid nesting parallel plans inside of other parallel > >>> plans. It's hard to imagine that being a win in a case like this, and > >>> it certainly adds a lot more cases to think about. > >> > >> I also think that avoiding nested parallel plans is a good step forward. > > > > Doing that as a part of the assess parallel safety patch was trivial, so I did. > > > > I tried with latest HEAD code, seems to be problem is present in other > scenarios. >
As mentioned previously [1], we have to do two different things to make this work, Robert seems to have taken care of one of those (basically second point in mail[1]) and still another one needs to be taken care which is to provide support of reading subplans in readfuncs.c and that will solve the problem you are seeing now. [1] - http://www.postgresql.org/message-id/ca+tgmobeqxztp4crqtx36mx7xtty-fsmfpuursvjoi8b6qr...@mail.gmail.com With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
