pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
2+ messages / 2 participants
[nested] [flat]
* ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
@ 2015-05-27 07:50 Tory M Blue <tmblue@gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: Tory M Blue @ 2015-05-27 07:50 UTC (permalink / raw)
To: pgsql-performance
Greetings and salutations.
I've got some weirdness.
Current:
Postgres 9.3.4
Slony 2.2.3
CentOS 6.5
Prior running Postgres 9.1.2 w/slony 2.1.3 CentOS 6.2
I found that if I tried to run a vacuum full on 1 table that I recently
reindexed (out of possibly 8 tables) that I get this error:
# vacuum full table.ads;
ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
If I run a vacuum analyze it completes fine, but I can't run a vacuum full
without it throwing an error. I seem to be able to query the table and I
seem to be able to add data to the table and slony seems fine as does
postgres.
I'm unclear why the vacuum full is failing with this error. I've done some
searching and there are hints to prior bugs, but I didn't catch anything in
9.3.3 to 9.3.7 that talks about this.
My next steps without your fine assistance, will be to drop the table from
slon and re-add it (meaning it will drop the table completely from this db
and recreate it from the master (there we can do a vacuum full without
failure)..
I have already tried to remove the indexes and just create those, but no
luck.
Ideas?
Thanks
Tory
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
@ 2015-05-27 22:02 Josh Berkus <josh@agliodbs.com>
parent: Tory M Blue <tmblue@gmail.com>
0 siblings, 0 replies; 2+ messages in thread
From: Josh Berkus @ 2015-05-27 22:02 UTC (permalink / raw)
To: pgsql-performance
On 05/27/2015 12:50 AM, Tory M Blue wrote:
> Greetings and salutations.
>
> I've got some weirdness.
>
> Current:
> Postgres 9.3.4
> Slony 2.2.3
> CentOS 6.5
>
> Prior running Postgres 9.1.2 w/slony 2.1.3 CentOS 6.2
>
> I found that if I tried to run a vacuum full on 1 table that I recently
> reindexed (out of possibly 8 tables) that I get this error:
>
> # vacuum full table.ads;
>
> ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
>
> If I run a vacuum analyze it completes fine, but I can't run a vacuum
> full without it throwing an error. I seem to be able to query the table
> and I seem to be able to add data to the table and slony seems fine as
> does postgres.
Is this happening on the Slony master or the replica?
There have been serveral bugs since 9.1.2 which could have caused this
particular error. Are you certain that this is a recent problem?
Note that this error affects just one compressed value or row, so you're
not losing other data, unless it's a symptom of an ongoing problem.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2015-05-27 22:02 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-05-27 07:50 ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 Tory M Blue <tmblue@gmail.com>
2015-05-27 22:02 ` Josh Berkus <josh@agliodbs.com>
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