ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881

From: Tory M Blue <tmblue(at)gmail(dot)com>
To: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881
Date: 2015-05-28 01:28:17
Message-ID: CAEaSS0apcecuf+2-e7U_sX1yeeAfaLn6D3VwhbCUWt-ytv+t+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sorry I think I posted this to the wrong group, sent to performance vs
General. My apologies to everyone in perf!

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
>
>
>
>

Browse pgsql-general by date

  From Date Subject
Next Message Robert Haas 2015-05-28 01:52:51 Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
Previous Message Alvaro Herrera 2015-05-28 01:19:57 Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1