Here's a link to a relevant thread that also shows how
to fix the problem, at least sufficiently to
successfully vacuum and/or dump the database.
This problem seems to be highly correlated with
versions in the 7.2.0 to 7.2.2 range, although AFAIK
no-one has ever traced it to a specific bug. We had
the same problem with our 7.2.1 installation, but have
been running fine with 7.2.4 for some months now.
--- Richard Huxton <dev@archonet.com> wrote:
> On Friday 20 Jun 2003 7:22 pm, Johnson, Shaunn
> wrote:
> > --howdy:
> >
> > --this is what i was talking about when doing
> > --things like 'vacuum' and 'pg_dump'.
> [snip]
> > Backing up schema for
> debborah_dev_bh_claimsum_4q02 ...
> > pg_dump: query to obtain list of indexes failed:
> ERROR: syscache lookup
> > for index 4185182890 failed
>
> As Tom said, if you're on 7.2.1, upgrade to 7.2.4
> immediately. Stop PG and
> take a backup of the entire data/base directory
> tree, Being paranoid, I'd set
> it up in parallel on a separaate machine or with a
> different PGDATA (and port
> etc). Then see if pg_dump for 7.2.4 can cope. There
> were a number of bugfixes
> between 7.2.1 and .4 - details in the release notes.
>
> --
> Richard Huxton
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the
> unregister command
> (send "unregister YourEmailAddressHere" to
majordomo@postgresql.org)
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com