| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | pryzby(at)telsasoft(dot)com, pgsql-hackers(at)postgresql(dot)org, noah(at)leadboat(dot)com |
| Subject: | Re: v13: CLUSTER segv with wal_level=minimal and parallel index creation |
| Date: | 2020-09-07 04:45:28 |
| Message-ID: | 20200907.134528.1788420979518620237.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Mon, 07 Sep 2020 00:33:03 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in
> Justin Pryzby <pryzby(at)telsasoft(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-09-07 05:08:18 | Re: proposal: possibility to read dumped table's name from file |
| Previous Message | Ian Barwick | 2020-09-07 04:33:56 | [doc] minor wording improvement in a couple of places |