Re: pg_upgrade issue upgrading 10 -> 13

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Sean Brown <sean(dot)brown(at)saminds(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_upgrade issue upgrading 10 -> 13
Date: 2020-10-01 17:02:53
Message-ID: 20201001170253.GB15909@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Oct 1, 2020 at 09:03:31AM -0700, Adrian Klaver wrote:
> 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 of pg_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.

And pg_dump (used by pg_upgrade) had little handling for such changes.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jonathan Strong 2020-10-01 17:41:31 Re: Rows removed on child table when updating parent partitioned table.
Previous Message Eduard Català 2020-10-01 16:59:37 Rows removed on child table when updating parent partitioned table.