pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David Modica <davidmo@imaginesoftware.com>
To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: binary upgade errors
Date: Thu, 14 Jun 2018 15:51:20 +0000
Message-ID: <7cb957dd12774a52ac8a680b73910c5b@imaginesoftware.com> (raw)

hi all. first time posting here.

I have been unsuccessfully trying to use pg_upgrade to upgrade from 9.6 to 10.4.

we have the uint extension in some of the databases. a combination of that extension

and probably how we have used it is causing the upgrade to fail. I will include the error msg.

can anyone with some experience please point me in the right direction to fix it ?

thanks,

david

output from pg_upgrade:
command: "/usr/pgsql-10.4/bin/pg_restore" --host /var/lib/pgsql/10.4 --port 50432 --username postgres --exit-on-error --verbose --dbname 'dbname=devel8' "pg_upgrade_dump_271840.custom" >> "pg_upgrade_dump_271840.log" 2>&1
pg_restore: connecting to database for restore
pg_restore: creating pg_largeobject "pg_largeobject"
pg_restore: creating pg_largeobject_metadata "pg_largeobject_metadata"
pg_restore: creating SCHEMA "its"
pg_restore: creating SCHEMA "public"
pg_restore: creating COMMENT "SCHEMA "public""
pg_restore: creating EXTENSION "uint"
pg_restore: creating COMMENT "EXTENSION "uint""
pg_restore: creating DOMAIN "its.adj_id_t"
pg_restore: creating DOMAIN "its.any_id_t"
pg_restore: creating DOMAIN "its.bigint_id_t"
pg_restore: creating SHELL TYPE "public.uint1"
pg_restore: creating FUNCTION "public.uint1in("cstring")"
pg_restore: creating FUNCTION "public.uint1out("public"."uint1")"
pg_restore: creating TYPE "public.uint1"
pg_restore: creating FUNCTION "public.uint1(integer)"
pg_restore: creating DOMAIN "its.bool_t"
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 4538; 1247 280489 DOMAIN bool_t postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  cannot cast type integer to public.uint1
    Command was:
-- For binary upgrade, must preserve pg_type oid
SELECT pg_catalog.binary_upgrade_set_next_pg_type_oid('280489'::pg_catalog.oid);

CREATE DOMAIN "its"."bool_t" AS "public"."uint1" DEFAULT (0)::"public"."uint1";

view thread (5+ messages)  latest in thread

Message-ID: <7cb957dd12774a52ac8a680b73910c5b@imaginesoftware.com>
Permalink:  ../7cb957dd12774a52ac8a680b73910c5b@imaginesoftware.com/
Also on:    postgresql.org/message-id/7cb957dd12774a52ac8a680b73910c5b@imaginesoftware.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: davidmo@imaginesoftware.com, pgsql-admin@lists.postgresql.org
  Subject: Re: binary upgade errors
  In-Reply-To: <7cb957dd12774a52ac8a680b73910c5b@imaginesoftware.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox