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 1m2ppB-0003hG-Ox for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Jul 2021 06:53:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m2pp9-0001Ra-Ix for pgsql-bugs@arkaria.postgresql.org; Mon, 12 Jul 2021 06:53:51 +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 1m2pp8-0001RS-6g for pgsql-bugs@lists.postgresql.org; Mon, 12 Jul 2021 06:53:51 +0000 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m2pp1-0007pK-NG for pgsql-bugs@lists.postgresql.org; Mon, 12 Jul 2021 06:53:49 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 78C875C010E; Mon, 12 Jul 2021 02:53:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Mon, 12 Jul 2021 02:53:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=Yl76/jClzGcX2EJWn1EiFqGN0D4 Nhl5hXv/XHXNon+4=; b=CVtfGsbbOZT4AEYDFNGiOnMyMOOF5ltlaRBFoj10C0J mjuVUQC34QRSCEPa/krb7owfvmS+oFDRprv8aaDHBSx2vb7JwdEet/pIUm2kuzKi MfDiuDgUg10NRFUUTfurAcgBhzipJY0MVQXfVWuS35KwA5Kn//YDpFSLIDNeZi0E fLsbh2d5kzuTBUVr+8MhspMveCV+NihWoPG/QsBo7wN54U267CswtDbBdaseFhxr G++BftrNQU7Teb/IZb8dn7/zKk8qFtJGrWft2PHRIFUly16XrhNbpu4UskSUltFB AMWFcFmyfsMT3z2PCB2Hggp4RQhnGLJ5Yzg7QOO2bCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=Yl76/j ClzGcX2EJWn1EiFqGN0D4Nhl5hXv/XHXNon+4=; b=vmUcj2k+AnNZWkYweEpy7r 1sb+uepe4D2CkrXu9yuNG2nsVzHiNWMx/9xXRkjWrtDMkyHI/8N7TvYHy55Z6A9O ETNa4Z4hT7YDmbt9rEKurHoqkivDd4my/8k0Dh0sTolMb0J531xQRRq5g1EX+UfB VoVUxkUZ4Ap5eJKhHr9Zhp8zBjRbRnuK/ZgrbduT3knJ+64eFdwcZVj86DbBVvJg D3blwUn8F1mChzk8O3g8AM3AEUYGQAGWa6ANC8m1QBz/AQkAqjXFXyYi1V6hEfsz /Gq1Z8Er/coQXw6s3HjgLXaUHC+7dmmAH+87er4sZ51uLN5j36DdSZ0wkNUzVwIA == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddugdduudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeffudeffeelgffhkedukeekvedv udfgieetkeekudelfeevhffhffdtudffieeutdenucffohhmrghinhepphhoshhtghhrvg hsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 12 Jul 2021 02:53:39 -0400 (EDT) Date: Mon, 12 Jul 2021 15:53:35 +0900 From: Michael Paquier To: Mohan Nagandlla Cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17093: invalid primary checkpoint record Message-ID: References: <17093-3d9fd04cfa74d04a@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6HK+dRWElw0N+V0o" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --6HK+dRWElw0N+V0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 12, 2021 at 11:06:23AM +0530, Mohan Nagandlla wrote: > Hi team > Any updates on this? > Again my server crashed because of invalid chek point . Your instance is, at short sight, corrupted, as the WAL segment holding the checkpoint record looked at the beginning of recovery should be flushed to disk. Please see here: https://wiki.postgresql.org/wiki/Corruption Also, note that using blindly pg_resetwal could cause corruptions in many ways. On top of that, it may be something that is wrong in your configuration. fsync = off could be an issue, for one. In short, it is not really possible to say what's wrong without knowing more how you are using PostgreSQL. -- Michael --6HK+dRWElw0N+V0o Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmDr5u8ACgkQnvQgOdby QH1pnQ//bYXB89PQ11WuBuWVxGDJrJQwDVyPkoG4OPI8P9a8EVhJvRYrNbC+q3jn 88xEdNVnVjXb1FHhAjCCAc+Z/QVS42lmi6xB8hCrRxkAVhA5gBYV5lKcpjpK2FhR YTgg0W3quTh/6sZbj6OZJeHr+5Q5PXPpCXE0rxFX2wi0bKdfPNvmsLckcOur4/1a +rQKVoOP0AWX3KPsoRsLbrY519F/1GiAFtLjaDaxrcMn91rD9xY+OBSU61iVLM8/ 9MLgBNT+CmuWI774B+hKFz72pekQz3ho2gk+I/kE5FKe6XOk/OLL+sJt6q1nAelj WGfzH7lA9J55Ua9LPAq7wJAaIpqLGtYtPvexrVPawrF1TOeXcOYCTCW6JZ0yXKwH 32/TBCRmqAK9wbIkbAAIFOL9YD6sO5CdBsumGLjs1sBWAMtb58pZihn2sS9+9DA4 /oAy/+6L5H7XGp61Q6UXfvVzKFe4TFtMvPP40YpbLOpT4nvsYOzaDNDE1H+Q7/K+ 8VlLDfXq/5fe8gRRa//kGaqwNgVSPE0D5YEtYsvvwtxF/0EY0aATgBVu1jLdeKZz +cIrK7sRWunTX/GlYzS7tQIH86YDRhUrZpmHiOQ1yGfWQmzD69Ib5m6JMrp8vx3q JpaqTf5i4E/nYuETls0FzSK6+6ZTNr0sLiA2irBy5+zUgMl3kVE= =VoPg -----END PGP SIGNATURE----- --6HK+dRWElw0N+V0o--