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 1pvxZD-0002n6-Pk for pgsql-general@arkaria.postgresql.org; Mon, 08 May 2023 09:54:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pvxZB-0007p0-HV for pgsql-general@arkaria.postgresql.org; Mon, 08 May 2023 09:54:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pvxZA-0007or-Fu for pgsql-general@lists.postgresql.org; Mon, 08 May 2023 09:54:01 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pvxZ7-001BLz-A3 for pgsql-general@postgresql.org; Mon, 08 May 2023 09:53:59 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id CD24A320027A; Mon, 8 May 2023 05:53:52 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Mon, 08 May 2023 05:53:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1683539632; x= 1683626032; bh=1nWHDTToQ5FlwilHy9tReYGOUtgwWd2lTB4+jI4+p4k=; b=A rlr+G/qvUk7NlJfjaIqF6fmwexVv5pq6kfpyt2ksfFH4nxBDiFCECMUZQs1/L4Jk nH0fkQ0P/nUJ2sWNQ/XevfYln+ssqVYC04TB8mjjUmRf/enAI6dmpVjqKU2YaIE7 GppbMVHG1247EOjwlrTcaKj5YwoVUoyA5RrRg5tpWsJMk3ds3qlYbQICxOkyInKT 8DrYBbSBSuoAS4x7QxNWLcQOUOg4PfdGk7b8U6sSpdqOD1X8sJAfSOvbIT0PATeH aLVhtSOr1UZ8sWPRjsRLiiz2M0lJ4LlIvyYWHM+eSHwKiA5jSU8POMYhYA0mY+/D ELAuACi7S0MCwggAPswug== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeefkedgvdduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 8 May 2023 05:53:51 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id ADBAE149; Mon, 8 May 2023 11:53:49 +0200 (CEST) Date: Mon, 8 May 2023 11:53:49 +0200 From: Alvaro Herrera To: Thomas Munro Cc: Evgeny Morozov , PostgreSQL General Subject: Re: "PANIC: could not open critical system index 2662" - twice Message-ID: <20230508095349.ie2sr3eldmtvuqcw@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-May-07, Thomas Munro wrote: > 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. If you > explicitly added STRATEGY=FILE_COPY to your CREATE DATABASE commands, > you'll get the traditional behaviour. Maybe it would be sensible to make STRATEGY_FILE=FILE_COPY the default again, for branch 15, before today's release. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Doing what he did amounts to sticking his fingers under the hood of the implementation; if he gets his fingers burnt, it's his problem." (Tom Lane)