Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wEppF-004SoH-1Y for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Apr 2026 14:42:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wEppE-003OH0-26 for pgsql-hackers@arkaria.postgresql.org; Mon, 20 Apr 2026 14:42:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wEppE-003OGp-19 for pgsql-hackers@lists.postgresql.org; Mon, 20 Apr 2026 14:42:12 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wEppC-00000001wAy-0sDZ for pgsql-hackers@lists.postgresql.org; Mon, 20 Apr 2026 14:42:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 63KEg6F0260902; Mon, 20 Apr 2026 10:42:06 -0400 From: Tom Lane To: Alvaro Herrera cc: Antonin Houska , Justin Pryzby , Mihail Nikalayeu , Andres Freund , Amit Kapila , Srinath Reddy Sadipiralla , Matthias van de Meent , pgsql-hackers@lists.postgresql.org, Robert Treat Subject: Re: Adding REPACK [concurrently] In-reply-to: References: Comments: In-reply-to Alvaro Herrera message dated "Mon, 20 Apr 2026 15:54:52 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <260900.1776696126.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 20 Apr 2026 10:42:06 -0400 Message-ID: <260901.1776696126@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > On 2026-Apr-20, Antonin Houska wrote: >> Is this an attempt to disable REPACK (CONCURRENTLY)? That would require >> wal_level=3Dminimal (due to commit 67c20979ce). In which way does REPAC= K seem to >> break test_plan_advice? > No, quite the contrary. That test normally runs with wal_level=3Dminima= l, > which causes REPACK to complain that it cannot start logical > decoding. So what you're saying is that the core regression tests will now fail with wal_level=3Dminimal? I don't see how that can possibly be considered acceptable from a global standpoint; we might as well remove wal_level=3Dminimal, because it will never again get tested. I think you need to move these tests out into some other test suite (or make a new one). regards, tom lane