pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
4+ messages / 4 participants
[nested] [flat]
* BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
@ 2022-01-27 20:57 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 4+ messages in thread
From: PG Bug reporting form @ 2022-01-27 20:57 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: padam.tehlan@leptonsoftware.com
The following bug has been logged on the website:
Bug reference: 17384
Logged by: Padam Tehlan
Email address: padam.tehlan@leptonsoftware.com
PostgreSQL version: Unsupported/Unknown
Operating system: Windows 2012 R2
Description:
Hi,
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.
Thanks!
Padam
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
@ 2022-02-03 04:42 Justin Pryzby <pryzby@telsasoft.com>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 4+ messages in thread
From: Justin Pryzby @ 2022-02-03 04:42 UTC (permalink / raw)
To: padam.tehlan@leptonsoftware.com; pgsql-bugs@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
@ 2022-02-03 04:50 Tom Lane <tgl@sss.pgh.pa.us>
parent: Justin Pryzby <pryzby@telsasoft.com>
0 siblings, 1 reply; 4+ messages in thread
From: Tom Lane @ 2022-02-03 04:50 UTC (permalink / raw)
To: Justin Pryzby <pryzby@telsasoft.com>; +Cc: padam.tehlan@leptonsoftware.com; pgsql-bugs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619
@ 2022-02-11 00:45 Andres Freund <andres@anarazel.de>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 4+ messages in thread
From: Andres Freund @ 2022-02-11 00:45 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Justin Pryzby <pryzby@telsasoft.com>; padam.tehlan@leptonsoftware.com; pgsql-bugs@lists.postgresql.org
Hi,
On 2022-02-02 23:50:41 -0500, Tom Lane wrote:
> (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.)
FWIW, in recent releases you can set allow_system_table_mods to on as a
superuser.
postgres[62458][1]=# TRUNCATE pg_statistic;
ERROR: 42501: permission denied: "pg_statistic" is a system catalog
LOCATION: truncate_check_rel, tablecmds.c:2159
postgres[62458][1]=# SET allow_system_table_mods = true;
SET
Time: 0.548 ms
postgres[62458][1]=# TRUNCATE pg_statistic;
TRUNCATE TABLE
postgres[62458][1]=# RESET allow_system_table_mods;
RESET
> 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.
Yea, hard to point somewhere concretely without more details.
Greetings,
Andres Freund
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2022-02-11 00:45 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-27 20:57 BUG #17384: ERROR: missing chunk number 0 for toast value 152073604 in pg_toast_2619 PG Bug reporting form <noreply@postgresql.org>
2022-02-03 04:42 ` Justin Pryzby <pryzby@telsasoft.com>
2022-02-03 04:50 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-02-11 00:45 ` Andres Freund <andres@anarazel.de>
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