pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Noah Misch <noah@leadboat.com>
To: cm@enterprisedb.com, Andrey Borodin <x4mmm@yandex-team.ru>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>
Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Date: Sun, 24 Oct 2021 16:35:02 -0700
Message-ID: <20211024233502.GA3960658@rfd.leadboat.com> (raw)
In-Reply-To: <20211024050028.GA3310519@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>

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.





view thread (107+ messages)  latest in thread

Message-ID: <20211024233502.GA3960658@rfd.leadboat.com>
Permalink:  ../20211024233502.GA3960658@rfd.leadboat.com/
Also on:    postgresql.org/message-id/20211024233502.GA3960658@rfd.leadboat.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: noah@leadboat.com, x4mmm@yandex-team.ru, pgsql-bugs@lists.postgresql.org, michael@paquier.xyz, tgl@sss.pgh.pa.us, pg@bowt.ie, andres@anarazel.de
  Subject: Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
  In-Reply-To: <20211024233502.GA3960658@rfd.leadboat.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox