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 1men1G-0007Cp-Od for pgsql-bugs@arkaria.postgresql.org; Sun, 24 Oct 2021 23:35:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1men1F-0001aB-GM for pgsql-bugs@arkaria.postgresql.org; Sun, 24 Oct 2021 23:35:13 +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 1men1F-0001Zx-1X for pgsql-bugs@lists.postgresql.org; Sun, 24 Oct 2021 23:35:13 +0000 Received: from mail-qk1-x735.google.com ([2607:f8b0:4864:20::735]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1men1B-0002c4-BY for pgsql-bugs@lists.postgresql.org; Sun, 24 Oct 2021 23:35:12 +0000 Received: by mail-qk1-x735.google.com with SMTP id h65so10441730qke.0 for ; Sun, 24 Oct 2021 16:35:08 -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=SE4kXBSl+0BW2eGDJbv2fIsqtP57pvKHWb4g06tayII=; b=NFZMsHHZfxynwgHIGun5XeCT0C/RAd/PsuJIHVgAej6FM3VrVXLL5DZaAhfhUI5C20 zvKq8VkEpdGrnwnKRnwJyVvzDPqH4S6HfBWBNX/jMtahE4RZ7IyAjGXLZ24NN5SKD5Ee A8eWUf63GRCZAw+HkMGwtgYBiWQwsAfEEQOFA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=SE4kXBSl+0BW2eGDJbv2fIsqtP57pvKHWb4g06tayII=; b=IeD/7LZvBpHDBar8uylyo9LgwVnzxABqfePxHLcbQwq5w9R7b5xNEo/1lko8pYXZlP oN4X2O6NT1DJ6DU9o5A1urXOcYlzClRDYhOClA50enotEAl8k/WnZmltaFcrBxbSella MQM/D0s7mbHKspqbtIOALzZSZ31RlqOBRBNGNq9TxgiY7duj0ybQriSgtWdfKKHapU61 NsB738axedR/mdNPy6uSbsrty4dbaV8f/tsJiOCJ7M2SMqZ9UAVq5451mBpDdf1jw/L+ tzFkvuXXdi9++gjIxe6a6lNrD9P2AE6XYDfaFjFqLHlffXwiYwCw5/ACkQvwxYD2NYVP 7URg== X-Gm-Message-State: AOAM530a5vf+B80D62881hGLMp5x8CsNzrshnBvPDj+NhRJuBpsCkG6+ JKqh8eTz7m9JBVC/lod0xdKzwQ== X-Google-Smtp-Source: ABdhPJyYoTHaQX7Dn3M3fqBCOsTw5PGQ1/nJeyFiHDXAE3OBIiXEi7FvxDMvPuJpM8cJwJSCIi3gUw== X-Received: by 2002:a05:620a:2403:: with SMTP id d3mr10888395qkn.348.1635118506762; Sun, 24 Oct 2021 16:35:06 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::46]) by smtp.gmail.com with ESMTPSA id bk13sm7829968qkb.58.2021.10.24.16.35.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 24 Oct 2021 16:35:05 -0700 (PDT) Date: Sun, 24 Oct 2021 16:35:02 -0700 From: Noah Misch To: cm@enterprisedb.com, Andrey Borodin Cc: PostgreSQL mailing lists , Michael Paquier , Tom Lane , Peter Geoghegan , Andres Freund Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data Message-ID: <20211024233502.GA3960658@rfd.leadboat.com> References: <20210829180913.ghojzzsgkqgm7vki@alap3.anarazel.de> <364BAA98-1A3F-4C39-B0D9-ED8C40EA902D@yandex-team.ru> <20210908064515.GA2496820@rfd.leadboat.com> <20210920044143.GA3414844@rfd.leadboat.com> <593C6C66-F19E-412A-9896-F1F5B272424A@yandex-team.ru> <20210925201012.GC4134968@rfd.leadboat.com> <20211017151205.GA2384251@rfd.leadboat.com> <9BA43784-E4A7-4638-900C-FC9868C388FA@yandex-team.ru> <20211019030212.GB3403374@rfd.leadboat.com> <20211024050028.GA3310519@rfd.leadboat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211024050028.GA3310519@rfd.leadboat.com> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Sat, Oct 23, 2021 at 10:00:28PM -0700, Noah Misch wrote: > Pushed. cm@enterprisedb.com, could you post a stack trace from buildfarm member gharial failing in "make check"? I'm looking for a trace from a SIGSEGV like those seen today: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gharial&dt=2021-10-24%2016%3A19%3A05 https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gharial&dt=2021-10-24%2020%3A38%3A39 Those SIGSEGV are all in ALTER TABLE. My commits from this thread probably broke something, but I've run out of ideas, and my hpux boxes died. https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=kittiwake&dt=2021-10-24%2012%3A01%3A10 got an interesting v9.6 failure, unrelated to the gharial SIGSEGV failures: 2021-10-24 14:25:29.263 CEST [34569:175] pgbench ERROR: could not read two-phase state from xlog at 0/158F4E0 2021-10-24 14:25:29.263 CEST [34569:176] pgbench STATEMENT: COMMIT PREPARED 'c1'; I don't see this thread's commits changing code paths relevant to that failure, so I currently think this one is a new test showing an old bug.