Re: BUG #9187: corrupt toast tables

Hello

I have a similar report:

2014-01-17 02:02:45 CET ERROR: missing chunk number 0 for toast value
26127 in pg_toast_20142
2014-01-17 02:02:45 CET STATEMENT: COPY journal.product_journal
(product_id, revision,
tablename, changes, create_user_id, item_id, created, processed,
process_user_id, confirmed) TO stdout;

PG 9.2.4

probably related
http://www.postgresql.org/message-id/C62EC84B2D3CF847899CCF4B589CCF70B20AA08F@BBMBX.backbone.local

Regards

Pavel

2014-02-11 22:19 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> kevin(dot)hughes(at)uk(dot)fujitsu(dot)com writes:
> > Sometime between the morning of the 31st of January and the morning of
> the
> > 3rd of February the database was corrupted. During that period there was
> > little or no activity - other than the nightly postgres dump
>
> > Looking at various logs we found this error: ERROR: unexpected chunk
> number
> > 110 (expected 106) for toast value 223972 in pg_toast_80768;
>
> FWIW, this type of error is sometimes due to corruption in the toast
> table's index, in which case you can fix it with a REINDEX. I'd try
> that before deleting data, anyway.
>
> Hard to tell what the actual underlying cause is :-(. I do note that
> you're running a PG version that's a year or so old. It'd be prudent
> to think about updating to 9.2.7 when that comes out next week.
>
> regards, tom lane
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>