Re: v13: CLUSTER segv with wal_level=minimal and parallel index creation

From: Noah Misch <noah(at)leadboat(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pryzby(at)telsasoft(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: v13: CLUSTER segv with wal_level=minimal and parallel index creation
Date: 2020-09-08 02:47:09
Message-ID: 20200908024709.GA3640955@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 08, 2020 at 10:43:32AM +0900, Kyotaro Horiguchi wrote:
> At Tue, 08 Sep 2020 09:13:53 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> > At Mon, 7 Sep 2020 02:32:55 -0700, Noah Misch <noah(at)leadboat(dot)com> wrote in
> > > As a PoC, this looks promising. Thanks. Would you add a test case such that
> > > the following demonstrates the bug in the absence of your PoC?
> > >
> > > printf '%s\n%s\n%s\n' 'log_statement = all' 'wal_level = minimal' 'max_wal_senders = 0' >/tmp/minimal.conf
> > > make check TEMP_CONFIG=/tmp/minimal.conf
> >
> > Mmm. I was close to add some tests to 018_wal_optimize.pl but your
> > suggestion seems better. I added several ines to create_index.sql.
> >
> > > Please have the test try both a nailed-and-mapped relation and a "nailed, but
> > > not mapped" relation. I am fairly confident that your PoC fixes the former
> > > case, but the latter may need additional code.
> >
> > Mmm. You're right. I choosed pg_amproc_fam_proc_index as
> > nailed-but-not-mapped index.
>
> I fixed a typo (s/staring/starting/).

At a glance, this looks reasonable. If a closer look doesn't reveal problems,
I'll push this.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-09-08 02:49:36 Re: Global snapshots
Previous Message Justin Pryzby 2020-09-08 02:39:16 Re: 回复:how to create index concurrently on partitioned table