From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: padam.tehlan@leptonsoftware.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
Date: Wed, 02 Feb 2022 23:50:41 -0500
Message-ID: <198233.1643863841@sss.pgh.pa.us> (raw)
In-Reply-To: <20220203044257.GH23027@telsasoft.com>
References: <17384-f50f2eedf541e512@postgresql.org>
<20220203044257.GH23027@telsasoft.com>
Justin Pryzby <pryzby@telsasoft.com> writes:
> On Thu, Jan 27, 2022 at 08:57:28PM +0000, PG Bug reporting form wrote:
>> Issue: ERROR: missing chunk number 0 for toast value 152073604 in
>> pg_toast_2619
>> we are facing issue with mentioned short description error while trying any
>> operation on database.
> From my notes from a handful of years ago, I think you'll have luck doing some
> things like this:
The good news is that that's the toast table for pg_statistic,
which means that there is exactly no irreplaceable data in it.
If all else fails, you can just truncate pg_statistic and then
re-ANALYZE the whole database to rebuild it.
(I say "just" truncate pg_statistic, but you'll have to do that
in a standalone backend started with the -O option, else there
are permissions checks that will prevent it.)
The bad news is that there might be more corruption lurking
elsewhere. What event precipitated this?
I think we have seen some bugs that would preferentially affect
pg_statistic, but not recently. If you're not running a current
minor release, an update is advisable.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pryzby@telsasoft.com, padam.tehlan@leptonsoftware.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
In-Reply-To: <198233.1643863841@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox