Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: padam(dot)tehlan(at)leptonsoftware(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
Date: 2022-02-03 04:42:57
Message-ID: 20220203044257.GH23027@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.
>
> We execute the various commands recommended in various blogs , given
> below-
> REINDEX table mytable;
> REINDEX table pg_toast.pg_toast_40948;
> VACUUM analyze mytable;
>
> Even after successful execution of the above commands, still when execute
> the Vacuum full its give error.
>
> Earlier response will be appreciable.

It sounds like the statistics for a catalog table are causing an error.

From my notes from a handful of years ago, I think you'll have luck doing some
things like this:

REINDEX TABLE pg_statistic;
VACUUM VERBOSE pg_statistic;
VACUUM FULL VERBOSE pg_statistic;
REINDEX INDEX pg_toast.pg_toast_2619_index;
REINDEX SCHEMA pg_toast;
REINDEX SYSTEM postgres; -- substitute the database name for postgres

BTW, what version postgres is this ?

How large are those tables?
SELECT pg_relation_size('pg_statistic'), pg_relation_size('pg_toast.pg_toast_2619_index');

--
Justin

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-02-03 04:50:41 Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
Previous Message Julien Rouhaud 2022-02-03 04:14:32 Re: Postgresql error : PANIC: could not locate a valid checkpoint record