Request a Demo
Home   >   mailing lists

Re: bug: Gather rescan keeps the first scan's tuple bound in workers - Mailing list pgsql-bugs

From shihao zhong
Subject Re: bug: Gather rescan keeps the first scan's tuple bound in workers
Date
Msg-id CAGRkXqRGE+TwD0Ttmb4b1J8Vy-drrkZYhh6hOf2_Uz5XKtXsEA@mail.gmail.com
Whole thread
In response to bug: Gather rescan keeps the first scan's tuple bound in workers  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-bugs
Tree view
Hi Jeff,

Thanks for reporting this bug.

I can reproduce this on master, and a 1000 row table is enough.
The attached 0001 adds a tuples_needed argument to
ExecParallelReinitialize() and stores it in the shared state, the same
way ExecInitParallelPlan() does.  0002 is a regression test and is
optional.

For the back branches this changes the signature of an exported
function.  I don't know of any extension that calls it, but if that is
a concern, a new function could set the bound there instead.

Thanks,
Shihao



Attachment

pgsql-bugs by date:

Previous
From: Srinath Reddy Sadipiralla
Date:
Subject: Re: BUG #19695: JSON_VALUE ... RETURNING jsonb returns NULL for later evaluation once one evaluation returns NULL
Next
From: shihao zhong
Date:
Subject: Re: JSON_SERIALIZE for JSONB returns parts of the internal JSONB representation