Re: Failure upgrading PG 9.2 to 9.3 - Mailing list pgsql-general

From Tom Lane
Subject Re: Failure upgrading PG 9.2 to 9.3
Date
Msg-id 17016.1395764392@sss.pgh.pa.us
Whole thread Raw
In response to Failure upgrading PG 9.2 to 9.3  (Sam Saffron <sam.saffron@gmail.com>)
Responses Re: Failure upgrading PG 9.2 to 9.3
List pgsql-general
Sam Saffron <sam.saffron@gmail.com> writes:
> Why would
> "ERROR:  operator does not exist: name !~ unknown"
> Come up ?

It's hard to explain that as anything except corrupted system catalogs
in your existing database :-(.  If you were really lucky, reindexing
pg_operator would fix it; but since pg_operator is usually pretty static,
it seems unlikely that it suffered index corruption.

> Any way to work around this?

Rather than relying on pg_upgrade, you could try using pg_dump(all)
to extract the data.  With some luck, pg_dump wouldn't be affected by
whatever has happened to the pg_operator catalog.

            regards, tom lane


pgsql-general by date:

Previous
From: Alan Hodgson
Date:
Subject: Re: Is it possible to "pip" pg_dump output into new db ?
Next
From: Joseph Kregloh
Date:
Subject: Re: Upgrading from 9.2 to 9.3 causes performance degradation