Re: Assertion failure with barriers in parallel hash join
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Melanie Plageman <melanieplageman@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-12T23:18:11Z
Lists: pgsql-hackers
On Tue, Oct 13, 2020 at 12:15 PM Melanie Plageman <melanieplageman@gmail.com> wrote: > On Thu, Oct 1, 2020 at 8:08 PM Thomas Munro <thomas.munro@gmail.com> wrote: >> On Tue, Sep 29, 2020 at 9:12 PM Thomas Munro <thomas.munro@gmail.com> wrote: >> Here's a throw-away patch to add some sleeps that trigger the problem, >> and a first draft fix. I'll do some more testing of this next week >> and see if I can simplify it. > > I was just taking a look at the patch and noticed the commit message > says: > > > With unlucky timing and parallel_leader_participation off... > > Is parallel_leader_participation being off required to reproduce the > issue? Yeah, because otherwise the leader detaches last so the problem doesn't arise.
Commits
-
Fix race in parallel hash join batch cleanup, take II.
- ef16d27245f6 11.20 landed
- 44d44aa9712f 12.15 landed
- 6e94d62e3f04 13.11 landed
- 1b9e42e82ae6 14.8 landed
- c03c6e8cf6a9 15.3 landed
- 8d578b9b2e37 16.0 landed
-
Revert "Fix race in Parallel Hash Join batch cleanup."
- 7f7f25f15edb 14.0 landed
- 492f6e21038a 11.12 landed
- b9ed85698f3e 12.7 landed
- 69739ec317ae 13.3 landed
-
Fix race in Parallel Hash Join batch cleanup.
- 0129c56fbe5c 11.12 landed
- 8fa2478b407e 12.7 landed
- 4e0f0995e923 13.3 landed
- 3b8981b6e1a2 14.0 landed
-
Mop-up for wait event naming issues.
- 3048898e73c7 13.0 cited