Re: Failure upgrading PG 9.2 to 9.3

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Sam Saffron <sam(dot)saffron(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Failure upgrading PG 9.2 to 9.3
Date: 2014-03-25 15:50:21
Message-ID: 5331A5BD.6070105@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 03/24/2014 04:58 PM, Sam Saffron wrote:
> I am getting the following failure on a customer DB upgrading 9.2 to 9.3
>
> Selecting previously unselected package postgresql-9.2.
> Unpacking postgresql-9.2 (from
> .../postgresql-9.2_9.2.8-1.pgdg12.4+1_amd64.deb) ...
> Processing triggers for postgresql-common ...
> Setting up postgresql-client-9.2 (9.2.8-1.pgdg12.4+1) ...
> Setting up postgresql-9.2 (9.2.8-1.pgdg12.4+1) ...
> Creating new cluster 9.2/main ...
> config /etc/postgresql/9.2/main
> data /var/lib/postgresql/9.2/main
> locale C
> port 5433
> * Starting PostgreSQL 9.2 database server
> ...done.
> * Stopping PostgreSQL 9.2 database server
> ...done.
> * Stopping PostgreSQL 9.3 database server
> ...done.
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions ok
> SQL command failed
> CREATE TEMPORARY TABLE info_rels (reloid) AS SELECT c.oid FROM
> pg_catalog.pg_class c JOIN pg_catalog.pg_namespace n ON
> c.relnamespace = n.oid LEFT OUTER JOIN pg_catalog.pg_index i ON
> c.oid = i.indexrelid WHERE relkind IN ('r', 'm', 'i', 'S') AND
> i.indisvalid IS DISTINCT FROM false AND i.indisready IS DISTINCT FROM
> false AND ((n.nspname !~ '^pg_temp_' AND n.nspname !~
> '^pg_toast_temp_' AND n.nspname NOT IN ('pg_catalog',
> 'information_schema', 'binary_upgrade', 'pg_toast') AND c.oid >=
> 16384) OR (n.nspname = 'pg_catalog' AND relname IN
> ('pg_largeobject', 'pg_largeobject_loid_pn_index',
> 'pg_largeobject_metadata', 'pg_largeobject_metadata_oid_index') ));
> ERROR: operator does not exist: name !~ unknown
> LINE 1: ...disready IS DISTINCT FROM false AND ((n.nspname !~ '^pg_te...
> ^
> HINT: No operator matches the given name and argument type(s). You
> might need to add explicit type casts.
>
>
> ----
>
> Why would
>
> "ERROR: operator does not exist: name !~ unknown"
>
> Come up ?
>
> Any way to work around this?

If you going from 9.2 --> 9.3 why are you installing 9.2?

Are you sure you are working in the right direction?

>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alan Hodgson 2014-03-25 16:19:15 Re: Is it possible to "pip" pg_dump output into new db ?
Previous Message Raymond O'Donnell 2014-03-25 15:46:18 Re: Is it possible to "pip" pg_dump output into new db ?