> "Lane, Tom" <[EMAIL PROTECTED]> writes:
>
> Ugh. Does it work if you do
>
> export PGOPTIONS="--ignore_system_indexes=1"
>
> first? If so, the problem would evidently be corruption of
> the indexes for pg_attribute, specifically
> pg_attribute_relid_attnum_index. It seems pretty su
"Lane, Tom" <[EMAIL PROTECTED]> writes:>
> "O'Shea, Brendan" <[EMAIL PROTECTED]> writes:
> >> "Lane, Tom" <[EMAIL PROTECTED]> writes:
> >> Ugh. Does it work if you do
> >> export PGOPTIONS="--ignore_system_indexes=1"
>
> > I tried that, but unfortunately pg_dump still fails to run
> and the err
"O'Shea, Brendan" <[EMAIL PROTECTED]> writes:
>> "Lane, Tom" <[EMAIL PROTECTED]> writes:
>> Ugh. Does it work if you do
>> export PGOPTIONS="--ignore_system_indexes=1"
> I tried that, but unfortunately pg_dump still fails to run and the error
> message is identical to previous attempts.
Huh. So
"O'Shea, Brendan" <[EMAIL PROTECTED]> writes:
> pg_dump: reading schemas
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: catalog is missing 9
> attribute(s) for relid 10297
Ugh. Does it work if you do
export PGOPTIONS="--ignore_system_indexes=1"
first? If so
We have run into a situation where our postgresql 8.2.5 database appears
to be corrupt and we are no longer able to run pg_dump. We don't know
what is causing the data corruption issues and unfortunately this is one
of those cases where we cannot reliably reproduce the problem (so no
test case can
