Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xOcX0-00000000Ez5-3tCY for pgsql-general@arkaria.postgresql.org; Wed, 04 Nov 2026 15:04:09 +0000 Received: from localhost ([127.0.0.1]:40606 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xOcX1-00000007FuK-1GRx for pgsql-general@arkaria.postgresql.org; Wed, 04 Nov 2026 15:04:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:60038) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xOcWv-00000007FuA-3zdb for pgsql-general@lists.postgresql.org; Wed, 04 Nov 2026 15:04:06 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xOcWs-00000000CkQ-0btS for pgsql-general@lists.postgresql.org; Wed, 04 Nov 2026 15:04:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 6A4F3sqn1589011; Wed, 4 Nov 2026 10:03:55 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 sss.pgh.pa.us 6A4F3sqn1589011 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sss.pgh.pa.us; s=default; t=1793804635; bh=k4zLcwXtMVkmcEfXPnWBx4roadhv+W6VC4ACx+kO2yA=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=tc4FNc8vep0mTwm2GrLQ/kdhgQAKPAjKILgTqvoD/W+t7B53VvW+c2KORrEUHzATb FkdXZ+8C0rNVmv8fISBog2cgcn6SO5sYiIFEml7Tkl3Ll1bUpbyQr+nTG0GQCyHSjt TlVRrggDRwE8IqWnZSsF2x174gUSXw+/dD1yw9JM= From: Tom Lane To: Laurenz Albe cc: loganathan P , pgsql-general@lists.postgresql.org Subject: =?UTF-8?Q?Re:_Application_Error_When_Accessing_the_Table_?= =?UTF-8?Q?=E2=80=93_PostgreSQL_15.18?= In-reply-to: References: Comments: In-reply-to Laurenz Albe message dated "Wed, 04 Nov 2026 08:27:55 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1589009.1793804634.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 04 Nov 2026 10:03:54 -0500 Message-ID: <1589010.1793804634@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: > On Wed, 2026-11-04 at 11:52 +0530, loganathan P wrote: >> While accessing the table through the application, I encountered the fo= llowing error. >> ERROR - missing chunk number 0 for toast value 55195659 in pg_toast_171= 559. > This is data corruption. Indeed, but you might be able to get out of it by REINDEX'ing that toast table, especially if you recently used REINDEX CONCURRENTLY on it. There's a recently-fixed bug that could lead to damaged toast indexes, though fortunately not to corruption of the tables themselves. regards, tom lane