From: Tom Lane <tgl@sss.pgh.pa.us>
To: Arjun Ranade <ranade@nodalexchange.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
Date: Tue, 31 Oct 2017 15:59:02 -0400
Message-ID: <13631.1509479942@sss.pgh.pa.us> (raw)
In-Reply-To: <CANrrCRwH9ZnW+XtOxozEUPqWuHrfNNqDw9K3H69k513i7-YryQ@mail.gmail.com>
References: <CANrrCRwH9ZnW+XtOxozEUPqWuHrfNNqDw9K3H69k513i7-YryQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Arjun Ranade <ranade@nodalexchange.com> writes:
> We had some downtime recently and I thought it would be a good idea to do a
> periodic VACUUM FULL of one of our large Postgres DB's.
> However, when I tried to attempt the VACUUM FULL, I saw the following error:
> INFO: vacuuming "pg_catalog.pg_statistic"
> vacuumdb: vacuuming of database "db1" failed: ERROR: missing chunk number
> 0 for toast value 30382746 in pg_toast_2619
We hear reports like this just often enough to make it seem like there's
some bug that afflicts pg_statistic specifically. Nobody's ever found
a cause though.
> Given that pg_statistic is inessential data (it can be rebuilt by analyzing
> each table), I did a 'DELETE FROM pg_statistic;' which removed all the
> rows.
That would've been my advice ...
> However, when I ran the VACUUM FULL again, I received the same error.
... but that's really interesting. Is this still reproducible? If you
could get a stack trace from the point of the error, that might yield
useful data. (Set a gdb breakpoint at "errfinish", run the VACUUM FULL,
and when it stops, get the stack with "bt". Don't use VERBOSE, or you'll
reach errfinish for each line of verbose output...)
Also, what PG version is this exactly?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ranade@nodalexchange.com
Subject: Re: Missing Chunk Error when doing a VACUUM FULL operation - DB Corruption?
In-Reply-To: <13631.1509479942@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