Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hLXgj-0006HI-W3 for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Apr 2019 18:41:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hLXgi-0000H0-Dw for pgsql-hackers@arkaria.postgresql.org; Tue, 30 Apr 2019 18:41:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hLXgi-0000Gq-5N for pgsql-hackers@lists.postgresql.org; Tue, 30 Apr 2019 18:41:08 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hLXgg-0005kU-37 for pgsql-hackers@lists.postgresql.org; Tue, 30 Apr 2019 18:41:07 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x3UIf0ZU016278; Tue, 30 Apr 2019 14:41:00 -0400 From: Tom Lane To: Andres Freund cc: Michael Paquier , Postgres hackers Subject: Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 In-reply-to: <20190430182741.s6o7mo5ebmgxxi5x@alap3.anarazel.de> References: <12189.1556575627@sss.pgh.pa.us> <20190429220924.lfptluzkujb26y2n@alap3.anarazel.de> <20190430030342.jmbgnih4q3cdoufz@alap3.anarazel.de> <26051.1556599053@sss.pgh.pa.us> <26528.1556599820@sss.pgh.pa.us> <20190430070552.jzqgcy4ihalx7nur@alap3.anarazel.de> <30579.1556639470@sss.pgh.pa.us> <20190430173457.pg6i6urvevse5jer@alap3.anarazel.de> <29546.1556647550@sss.pgh.pa.us> <20190430182741.s6o7mo5ebmgxxi5x@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Tue, 30 Apr 2019 11:27:41 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16276.1556649660.1@sss.pgh.pa.us> Date: Tue, 30 Apr 2019 14:41:00 -0400 Message-ID: <16277.1556649660@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2019-04-30 14:05:50 -0400, Tom Lane wrote: >> Possibly we could run them in a TAP test that configures a cluster >> with autovac disabled? > Hm. Would it be sufficient to instead move them to a non-concurrent > test group, and stick a BEGIN; LOCK pg_class, ....; COMMIT; around it? Doubt it. Maybe you could get away with it given that autovacuum and autoanalyze only do non-transactional updates to pg_class, but that seems like a pretty shaky assumption. > This is a pretty finnicky area of the code, with obviously not enough > test coverage. I'm inclined to remove them from the back branches, and > try to get them working in master? I think trying to get this "working" is a v13 task now. We've obviously never tried to stress the case before, so you're neither fixing a regression nor fixing a new-in-v12 issue. regards, tom lane