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 1oKNIC-0004Zv-Ly
	for pgsql-admin@arkaria.postgresql.org; Sat, 06 Aug 2022 17:08:52 +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 1oKNIA-00060D-FI
	for pgsql-admin@arkaria.postgresql.org; Sat, 06 Aug 2022 17:08:50 +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 <tgl@sss.pgh.pa.us>)
	id 1oKNIA-0005dY-2m
	for pgsql-admin@lists.postgresql.org; Sat, 06 Aug 2022 17:08:50 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oKNI4-0006iC-GC
	for pgsql-admin@lists.postgresql.org; Sat, 06 Aug 2022 17:08:49 +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 276H8frS121034;
	Sat, 6 Aug 2022 13:08:41 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: manoj kathar <manojkathar3@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: error : missing chunk number 3 for toast value 14146136 in
 pg_toast_8895383
In-reply-to: 
 <CAGYwLFj_1CLuu3EF+ZdTMNnatvRWsuJ3KXDKLRBUbiYt3uQzTg@mail.gmail.com>
References: 
 <CAGYwLFj_1CLuu3EF+ZdTMNnatvRWsuJ3KXDKLRBUbiYt3uQzTg@mail.gmail.com>
Comments: In-reply-to manoj kathar <manojkathar3@gmail.com>
	message dated "Sat, 06 Aug 2022 22:26:11 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <121032.1659805721.1@sss.pgh.pa.us>
Date: Sat, 06 Aug 2022 13:08:41 -0400
Message-ID: <121033.1659805721@sss.pgh.pa.us>
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/121033.1659805721%40sss.pgh.pa.us>
Precedence: bulk

manoj kathar <manojkathar3@gmail.com> writes:
> We are performing the PostgreSQL DB upgrade using pg_upgrade from 9.6 to
> 12.5 on the production server.

What is the rationale for choosing 12.5?  The current v12-branch release
is 12.11 (and 12.12 will be out next week).  So you're missing nearly
two years' worth of bug fixes.  A quick look through the release notes
shows at least one pg_upgrade fix that could be relevant, from 12.8:

      Make <application>pg_upgrade</application> carry forward the old
      installation's <literal>oldestXID</literal> value (Bertrand Drouvot)

			regards, tom lane