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 1pvT5r-0003Cv-L3 for pgsql-general@arkaria.postgresql.org; Sun, 07 May 2023 01:21:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pvT5p-0001Ll-Dk for pgsql-general@arkaria.postgresql.org; Sun, 07 May 2023 01:21:41 +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 1pvT5p-0001H7-2t for pgsql-general@lists.postgresql.org; Sun, 07 May 2023 01:21:41 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pvT5h-0012LB-Rl for pgsql-general@postgresql.org; Sun, 07 May 2023 01:21:40 +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 3471LUpj4029099; Sat, 6 May 2023 21:21:30 -0400 From: Tom Lane To: Thomas Munro cc: Evgeny Morozov , PostgreSQL General Subject: Re: "PANIC: could not open critical system index 2662" - twice In-reply-to: References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com> <8486f71f9c11e98af787e15e2d2ed0ecfdbf6ee7.camel@cybertec.at> <010201877eb3c125-d9aff979-cad6-407b-8b4e-012487666088-000000@eu-west-1.amazonses.com> <01020187e773e031-eecea370-714f-4858-82e5-ed1c9091eb6f-000000@eu-west-1.amazonses.com> <01020187e7f5a96c-9bd4497c-abff-4c91-8a3f-e751a1f7d4b4-000000@eu-west-1.amazonses.com> <01020187eae42315-1cc83aed-2b4f-4c9e-ae36-ee82778f7154-000000@eu-west-1.amazonses.com> <01020187f07f341f-d1593cf8-4fc7-4186-b70c-0c8862a2aa32-000000@eu-west-1.amazonses.com> <0102018! 7f109fdd0-a5cfdb9a-6118-430f-b052-0d720f57620b-000000@eu-west-1.amazonses.com> Comments: In-reply-to Thomas Munro message dated "Sun, 07 May 2023 09:13:20 +1200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4029097.1683422490.1@sss.pgh.pa.us> Date: Sat, 06 May 2023 21:21:30 -0400 Message-ID: <4029098.1683422490@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > Did you previously run this same workload on versions < 15 and never > see any problem? 15 gained a new feature CREATE DATABASE ... > STRATEGY=WAL_LOG, which is also the default. I wonder if there is a > bug somewhere near that, though I have no specific idea. Per the release notes I was just writing ... Fix potential corruption of the template (source) database after CREATE DATABASE with the STRATEGY WAL_LOG option (Nathan Bossart, Ryo Matsumura) Improper buffer handling created a risk that any later modification of the template's pg_class catalog would be lost. The comment about only pg_class being affected is my interpretation of what the commit message said, but I might have misunderstood. regards, tom lane