pg_upgrade failure upgrading from v10.8 to v14.4 - Mailing list pgsql-admin

From Murthy Nunna
Subject pg_upgrade failure upgrading from v10.8 to v14.4
Date
Msg-id DM8PR09MB667740FCD23BCFECA20E8A3CB8909@DM8PR09MB6677.namprd09.prod.outlook.com
Whole thread Raw
Responses Re: pg_upgrade failure upgrading from v10.8 to v14.4
List pgsql-admin

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",

 

 

pgsql-admin by date:

Previous
From: Raj kumar
Date:
Subject: Query to check Progress of Alter Statements PostgreSQL
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_upgrade failure upgrading from v10.8 to v14.4