Re: v13: CLUSTER segv with wal_level=minimal and parallel index creation
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: tgl@sss.pgh.pa.us
Cc: pryzby@telsasoft.com, pgsql-hackers@postgresql.org, noah@leadboat.com
Date: 2020-09-07T04:45:28Z
Lists: pgsql-hackers
At Mon, 07 Sep 2020 00:33:03 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote in > Justin Pryzby <pryzby@telsasoft.com> writes: > > This is easily reproduced, at least on pg_attribute Thanks for the repro. > Yeah, duplicated here. The assertion (not SIGSEGV) is in code > added by c6b92041d, so it seems clearly an open issue for v13. > > I did not check to see what happens in a non-assert build. The cause is that the worker had received pending-sync entry correctly but not never created a relcache entry for the relation using RelationBuildDesc. So the rd_firstRelfilenodeSubid is not correctly set. I'm investigating it. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Fix rd_firstRelfilenodeSubid for nailed relations, in parallel workers.
- 6f15be5bedfc 13.0 landed
- fe4d022c8e17 14.0 landed
-
Skip WAL for new relfilenodes, under wal_level=minimal.
- c6b92041d385 13.0 cited