On Wed, Jun 7, 2017 at 6:36 AM, Amit Kapila <amit.kapil...@gmail.com> wrote: > I don't think so because this problem has been reported previously as > well [1][2] even before the commit in question. > > [1] - > https://www.postgresql.org/message-id/1ce5a19f-3b1d-bb1c-4561-0158176f65f1%40dunslane.net > [2] - https://www.postgresql.org/message-id/25861.1472215822%40sss.pgh.pa.us
Oh, good point. So this is a longstanding bug that has possibly just gotten easier to hit. I still think figuring out what's going on with the ParallelWorkerNumbers is a good plan. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
