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 <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1m6Fii-0006Ye-0p
	for pgsql-admin@arkaria.postgresql.org; Wed, 21 Jul 2021 17:09:20 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1m6Fig-0000xQ-OH
	for pgsql-admin@arkaria.postgresql.org; Wed, 21 Jul 2021 17:09:18 +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 <scott_ribe@elevated-dev.com>)
	id 1m6Fig-0000wK-F8
	for pgsql-admin@lists.postgresql.org; Wed, 21 Jul 2021 17:09:18 +0000
Received: from mailout.easymail.ca ([64.68.200.34])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <scott_ribe@elevated-dev.com>)
	id 1m6Fib-0002xQ-KP
	for pgsql-admin@lists.postgresql.org; Wed, 21 Jul 2021 17:09:17 +0000
Received: from localhost (localhost [127.0.0.1])
	by mailout.easymail.ca (Postfix) with ESMTP id DC7A7C0CB3;
	Wed, 21 Jul 2021 17:09:10 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at emo04-pco.easydns.vpn
Received: from mailout.easymail.ca ([127.0.0.1])
	by localhost (emo04-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id A7Q6kbAM74Dk; Wed, 21 Jul 2021 17:09:10 +0000 (UTC)
Received: from smtpclient.apple (unknown [4.28.96.150])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mailout.easymail.ca (Postfix) with ESMTPSA id 24E57C21EC;
	Wed, 21 Jul 2021 17:09:08 +0000 (UTC)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Subject: Re: Data corruption
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <MA1PR01MB0634DD078065C4D8E14DDB64E0E39@MA1PR01MB0634.INDPRD01.PROD.OUTLOOK.COM>
Date: Wed, 21 Jul 2021 11:09:07 -0600
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <17C82666-5695-4AD0-AA82-5B4BA9E256A4@elevated-dev.com>
References: 
 <CAGHa9HXONb+ayki84FrNW1cVLuWrkv_=1q+HAngq923GBvnUgw@mail.gmail.com>
 <CAM+6J97ueqECOkQbKtLp2o1A-Ys1mYAfhP0qpaiKbuv7QRa_pA@mail.gmail.com>
 <MA1PR01MB0634DD078065C4D8E14DDB64E0E39@MA1PR01MB0634.INDPRD01.PROD.OUTLOOK.COM>
To: Vijaykumar Jain <vijaykumarjain.github@gmail.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/17C82666-5695-4AD0-AA82-5B4BA9E256A4%40elevated-dev.com>
Precedence: bulk

Do you have any clue as to how this happened?

If you have a hardware problem, disk, controller or cable that is =
corrupting data written, then any efforts you make at recovery on the =
same hardware could just result in more & more corruption.

You don't mention, I think, whether you've copied the data to different =
storage (and preferably different server), but if you haven't already =
done so, STOP RIGHT NOW and do nothing else with this db until you've =
done that.