Re: pg_upgrade issue upgrading 10 -> 13 - Mailing list pgsql-general

From Adrian Klaver
Subject Re: pg_upgrade issue upgrading 10 -> 13
Date
Msg-id bbfe4ac5-474f-353a-7c2a-86474aba866e@aklaver.com
Whole thread Raw
In response to pg_upgrade issue upgrading 10 -> 13  (Sean Brown <sean.brown@saminds.com>)
Responses Re: pg_upgrade issue upgrading 10 -> 13  (Bruce Momjian <bruce@momjian.us>)
List pgsql-general
On 10/1/20 7:51 AM, Sean Brown wrote:
> I’m having a little problem using pg_upgrade to move from 10 to 13, I’m assuming the issue is related to the removal
ofpg_pltemplate, but I can’t find anything related to how to handle it.
 
> 
> pg_upgrade —check reports that the clusters are compatible, but the actual upgrade fails starting the new cluster
with-
 
> 
> ERROR: relation “pg_catalog.pg_pltemplate” does not exist
> STATEMENT: GRANT SELECT ON TABLE “pg_catalog"."pg_pltemplate” TO "appuser”;

Which points to the dangers of doing things to the system tables. They 
can change/disappear between major versions.

> 
> Is there a way to deal with this that doesn’t include dropping the source table?
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com



pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade issue upgrading 10 -> 13
Next
From: Eduard Català
Date:
Subject: Rows removed on child table when updating parent partitioned table.