Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kFTfD-0001dM-U7 for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Sep 2020 02:47:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kFTfC-0005eH-6d for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Sep 2020 02:47:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kFTfB-0005e6-Oz for pgsql-hackers@lists.postgresql.org; Tue, 08 Sep 2020 02:47:17 +0000 Received: from mail-pg1-x542.google.com ([2607:f8b0:4864:20::542]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kFTf9-0001Pt-Bi for pgsql-hackers@postgresql.org; Tue, 08 Sep 2020 02:47:17 +0000 Received: by mail-pg1-x542.google.com with SMTP id 67so8983835pgd.12 for ; Mon, 07 Sep 2020 19:47:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=EzSgfpN8WAhVIvDZggXfeR537dffCWNMAQt/3RRf0VU=; b=bs9hZC3AT6tS7FtHRSQajgGqwkKZmYPqa3PKlbKPeGRXvIEPZiK8NPY0vqQ3nyog8v B0bDOfGNAEnbmIED3OwdCH58SFlxpeOOZctpbi4yHLtsBZH0EkCRa5BoW/ssNOCO40CC OWAcYVBMb9ZcaLv3/VsfRacGk17la3r2OPFyg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=EzSgfpN8WAhVIvDZggXfeR537dffCWNMAQt/3RRf0VU=; b=aFGwd4rrhiCsmMpQrSDemLjajenZP62DyPZIDs/zQ/wi0N1ExASJaqhW6NUFq1AyvL jEdcfVf4DRTJ7JUPn8qDzUh3eBcy1nnIi6DHcQChtF47m8tS8WV7TSSGOFYaazONS/DG wHPkas6htCokBQVtzo0Ab3DPwWeeDN8Tvzcjy5BlufZ+a99bfo2FetyFYJiHOXJrsMk0 /FBu185wbwwh3VgiifRzz+wj5pop3XMYWUvTgQcEv17MikiA9u6kFYVaxNUXlzjjAkU6 SMsQKO9o6QgQvDnrwRkgccWw8TOIun+58+s8GRvfGoqFgCF3EESxLSrc17ismnE/rueo ZQPA== X-Gm-Message-State: AOAM532xsSnXtQkDpqXeAhE9wV30FFkxiGkkg/1q8WvnZJC7YzvHt8gn nf6PEV4EIQQJ2yATPjvmOxK3Xg== X-Google-Smtp-Source: ABdhPJxeUbooGeM6lsybYOSZcTY45DWWepIWB5BPszVXyeGlpCAI1Zz4YWX0XggUA2GEnTT3v7TFQg== X-Received: by 2002:a63:4c22:: with SMTP id z34mr18834069pga.370.1599533232342; Mon, 07 Sep 2020 19:47:12 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::43]) by smtp.gmail.com with ESMTPSA id e19sm17144888pfl.135.2020.09.07.19.47.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 Sep 2020 19:47:11 -0700 (PDT) Date: Mon, 7 Sep 2020 19:47:09 -0700 From: Noah Misch To: Kyotaro Horiguchi Cc: tgl@sss.pgh.pa.us, pryzby@telsasoft.com, pgsql-hackers@postgresql.org Subject: Re: v13: CLUSTER segv with wal_level=minimal and parallel index creation Message-ID: <20200908024709.GA3640955@rfd.leadboat.com> References: <20200907.174036.603784943439284546.horikyota.ntt@gmail.com> <20200907093255.GA3609623@rfd.leadboat.com> <20200908.091353.1505164218636547516.horikyota.ntt@gmail.com> <20200908.104332.1790214922230554649.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200908.104332.1790214922230554649.horikyota.ntt@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 wrote in > > At Mon, 7 Sep 2020 02:32:55 -0700, Noah Misch 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.