Re: (pgsql8.4) DATA Corruption

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Mikola Rose <mrose(at)power-soft(dot)com>
Cc: "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: (pgsql8.4) DATA Corruption
Date: 2011-08-19 20:02:16
Message-ID: CAOR=d=05dcTFyV2zv1hPjUu4iTXT1w+sTySErF-PrmmB9jT=9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

On Fri, Aug 19, 2011 at 1:08 PM, Mikola Rose <mrose(at)power-soft(dot)com> wrote:
> Happy Friday people!
>
>
>
> I was wondering if anyone had any suggestions on how to resolve this
> issue...  I am moving otrs to another server and during the backup process I
> am running into this error
>
> pg_dump: dumping contents of table article_attachment
>
>
>
>
>
> pg_dump: SQL command failed
>
> pg_dump: Error message from server: ERROR:  unexpected chunk number 7
> (expected 6) for toast value 77281 in pg_toast_57366
>
>
>
>
>
> pg_dump: The command was: COPY public.article_attachment (id, article_id,
> filename, content_size, content_type, content, create_time, create_by,
> change_time, change_by, content_id, content_alternative) TO stdout;
>
>
>
>
>
> pg_dump: *** aborted because of error
>
>
>
>
>
> I have tried a vacuum and reindex with no successes.

You'll likely have to figure which blocks are corrupted, and copy out
the good data using a where clause the excludes it, then get what you
can out of it, truncate the table, and reinsert the data.

Then figure out what part of your hardware is / might be dodgy. mem
test, disk check, etc.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Mik Rose 2011-08-19 20:27:57 Re: (pgsql8.4) DATA Corruption
Previous Message Mikola Rose 2011-08-19 19:08:09 (pgsql8.4) DATA Corruption