Re: Failure upgrading PG 9.2 to 9.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sam Saffron <sam(dot)saffron(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Failure upgrading PG 9.2 to 9.3
Date: 2014-03-25 16:19:52
Message-ID: 17016.1395764392@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sam Saffron <sam(dot)saffron(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joseph Kregloh 2014-03-25 17:25:05 Re: Upgrading from 9.2 to 9.3 causes performance degradation
Previous Message Alan Hodgson 2014-03-25 16:19:15 Re: Is it possible to "pip" pg_dump output into new db ?