From: Murthy Nunna <mnunna@fnal.gov>
To: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: pg_upgrade failure upgrading from v10.8 to v14.4
Date: Fri, 22 Jul 2022 16:19:42 +0000
Message-ID: <DM8PR09MB667740FCD23BCFECA20E8A3CB8909@DM8PR09MB6677.namprd09.prod.outlook.com> (raw)
Folks,
I am testing upgrade of my cluster from version 10.8 to 14.4
I encountered following error. Any help or insight is much appreciated.
Thanks.
*failure*
Consult the last few lines of "pg_upgrade_dump_16400.log" for
the probable cause of the failure.
Last few lines of pg_upgrade_dump_16400.log:
pg_restore: error: could not execute query: ERROR: column c.relhaspkey does not exist
LINE 19: "c"."relhaspkey" AS "haspkey",
^
Command was:
-- For binary upgrade, must preserve pg_type oid
SELECT pg_catalog.binary_upgrade_set_next_pg_type_oid('16681'::pg_catalog.oid);
-- For binary upgrade, must preserve pg_type array oid
SELECT pg_catalog.binary_upgrade_set_next_array_pg_type_oid('16680'::pg_catalog.oid);
-- For binary upgrade, must preserve pg_class oids
SELECT pg_catalog.binary_upgrade_set_next_heap_pg_class_oid('16679'::pg_catalog.oid);
CREATE VIEW "public"."all_tables" AS
SELECT ((("n"."nspname")::"text" || '.'::"text") || ("c"."relname")::"text") AS "tablename",
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: mnunna@fnal.gov
Subject: Re: pg_upgrade failure upgrading from v10.8 to v14.4
In-Reply-To: <DM8PR09MB667740FCD23BCFECA20E8A3CB8909@DM8PR09MB6677.namprd09.prod.outlook.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