Re: Upgrading postgresql-8.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Steve Erickson <serickson(at)digitiliti(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Upgrading postgresql-8.4
Date: 2013-03-11 17:10:25
Message-ID: 20297.1363021825@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Steve Erickson <serickson(at)digitiliti(dot)com> writes:
> This went well and postgres restarted just fine. However, now when I execute a pg_dump I get a missing chunk 0 for pg_toast_2619 while querying pg_attribute. I did a reindex on pg_toast_2619, then tried to VACUUM ANALYZE pg_attribute but again got the missing chunk 0 error.

> Did I miss a step doing the upgrade or recovery attempt, or is the
> data corrupted?

It's corrupt, but fortunately for you, 2619 is pg_statistic which is
eminently discardable data. Just truncate pg_statistic and you should
be good. If you aren't immediately abandoning the old database, you
might want to re-ANALYZE everything to reconstruct the stats.

We've seen one or two reports like this before, which makes me think
there might be a reproducible bug lurking somewhere around here; but
I don't suppose you have a recipe for getting a database into this
state ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Steve Erickson 2013-03-11 17:39:00 Re: Upgrading postgresql-8.4
Previous Message Stefan Keller 2013-03-11 16:15:35 Re: How to append an element to a row inside a 2-dim. array?