Thanks heaps Tom, I can confirm corrupt db upgrades fine with pg_dump. Was wondering if there are any plans to add a --no-validate to pg_upgrade, since the crash seems only to happen during validation. Cheers Sam On Wed, Mar 26, 2014 at 3:19 AM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Sam Saffron <sam.saffron@xxxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
