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 1pmOT2-0003rl-3I for pgsql-general@arkaria.postgresql.org; Wed, 12 Apr 2023 00:36:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pmOT1-00043J-1A for pgsql-general@arkaria.postgresql.org; Wed, 12 Apr 2023 00:36:07 +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 1pmOT0-000439-MV for pgsql-general@lists.postgresql.org; Wed, 12 Apr 2023 00:36:06 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmOSy-0001aA-Fd for pgsql-general@postgresql.org; Wed, 12 Apr 2023 00:36:05 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id E834832009CB; Tue, 11 Apr 2023 20:36:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 11 Apr 2023 20:36:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1681259762; x=1681346162; bh=4X FHtzaludlZaT8/dlnggKlq3dNgpti+0IorOUVjtwE=; b=dckNbkcCLsd3+DYVGX Cs7R1dS/HM2/PjtPFEfS6YcqjcbVke9VAvnyk2kIMfatS1w9/mSZO3h/97tVtS40 S6HV0ZqZ99n5SjUjBoWaeuT2nyC6J1fOJIymWb7szHmNTLhWi0FCbtsDgKs8RdWA +9AnmV1/KlTuOnF5rQw9SkQsE2amw76hlalQ+u9cp+DfmcdK/W2Eqr0HC6JR36uB 0spe21d/ucUsSHv+yyUNUgiWq9Ci2s0PvuwSrfsc5u9FhY+NRrnz2jRgqAA6Ftou DHUnns63j2bm4Ac1cDy4YmyL1AQMg8mxgOmbHTS1jUz0zj2N/FoQ8ski//e6wZia 2R8w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references: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=1681259762; x=1681346162; bh=4XFHtzaludlZa T8/dlnggKlq3dNgpti+0IorOUVjtwE=; b=SElUr7YzSgQga1e/RRKHKpthOEs00 YSu1w9gppbLNhF4+JwgfF9y0wYXr2VQ0fULb6DD2viSbkr0k5+DhrUBTKJysaQWk FiB7C2PLAwE4Gc7Zt4YlE6+c3jYHe3F4oHaBrlkwPhaGQzA/TmDdi3JznoATBKYC kupkxTzCbCDOAOMaw1mfluJWQgdXvVtGDt7LoVH42UeUREyzPPofiW3bn84Z7ydr QnvZx7UAT+1mTNTrZ8a2aDO6KRJSU4JYFJCOzr3dvSgiPHsV8xUK9VzkNBwskHHS n3HiQbWQ6j/gNLunBIaGhHlOX3MUeM/0pEBFzmIcGarIUNw4kDEEiihSg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdekhedgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 11 Apr 2023 20:35:59 -0400 (EDT) Date: Wed, 12 Apr 2023 09:35:56 +0900 From: Michael Paquier To: Evgeny Morozov Cc: Laurenz Albe , PostgreSQL General , "Peter J. Holzer" Subject: Re: "PANIC: could not open critical system index 2662" - twice Message-ID: References: <01020187577238cf-da8c0f4a-3ab9-445a-8c74-31ef51439f30-000000@eu-west-1.amazonses.com> <4f4ab16320d7b3a4e9950eaabde752dce204dc77.camel@cybertec.at> <010201877134be1c-fb837249-04a1-4cb0-a13f-c542425b50a0-000000@eu-west-1.amazonses.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DnnZeaMCEN8/9Ljv" Content-Disposition: inline In-Reply-To: <010201877134be1c-fb837249-04a1-4cb0-a13f-c542425b50a0-000000@eu-west-1.amazonses.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --DnnZeaMCEN8/9Ljv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 11, 2023 at 04:44:54PM +0000, Evgeny Morozov wrote: > We have data_checksums=on. (It must be on by default, since I cannot > find that in our config files anywhere.) initdb does not enable checksums by default, requiring a -k/--data-checksums, so likely this addition comes from from your environment. > However, the docs say "Only > data pages are protected by checksums; internal data structures and > temporary files are not.", so I guess pg_class_oid_index might be an > "internal data structure"? pg_class_oid_index is a btree index that relies on 8k on-disk pages (default size), so it is subject to the same rules as normal relations regarding checksums for the pages flushed to disk, even if it is on a catalog. -- Michael --DnnZeaMCEN8/9Ljv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmQ1/OwACgkQnvQgOdby QH0izxAAh/ZcwM+Zv9wyef1O4KTpIzWy/TVcWZVO8zZtgEMC+fmC3ELVdGm29ovD hLeYUAgYyPBOJLExYYcYHRjGEodNjMzvFZZ22n0LVKRGEi6ej+xsnqpMfvEUQ76P N6Ae6LUcQzGYPV0J4klbzhHvxhuK/HW2efYGLTg7o7rjV/ZIe2ASu2eNeZV1QFbE 4pSk6vQYB/YesNmnLG7x08pEzqgkKmphz1H9nYFtdGNHzjA4N3vfz7oWfouOAZJn vIhwfN94a0oaFD7F17dZ+mNDeaO77y70kmoaWBM62dhRYX6q5iec1ciBrhEjN2Zb r48IjXPyXEeh/aoQqPtb+RoGDh32nZLaBAUXj5TNN+o9egH9IMru9Kw6aZGsj/Fl 2E+uUVOm717NoI6pTYxRhQCaCNrUjq7+OfhIB8fgSlD1uzIAJEvTmAPCHMyO6uBW 9M7xZ+Z1+C3nBIZA0CVt3gNjbdPb8ZaeFIKiPsJ6AlhIQAerIffgiBJTzhHHvkXj yWwkRgP9tPePChN1k6LsIiNH7bTubMD1R42EkZDOXpZTTHnWHlLb/AAdI6xSSnmq Wur/vhqyD9PaQ0VovGL6Koz56MPJObO9ws0NP8ZR4crT/d+8uhUFs7Z9HbtLVhX1 sxtWa6wzMXBI+/SJzismqolhfXqct+EY76P4MNgsraYQ1dzA6nQ= =ZV0t -----END PGP SIGNATURE----- --DnnZeaMCEN8/9Ljv--