From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | 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 16:03:31 |
Message-ID: | bbfe4ac5-474f-353a-7c2a-86474aba866e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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 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.
>
> Is there a way to deal with this that doesn’t include dropping the source table?
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Eduard Català | 2020-10-01 16:59:37 | Rows removed on child table when updating parent partitioned table. |
Previous Message | Bruce Momjian | 2020-10-01 15:43:52 | Re: pg_upgrade issue upgrading 10 -> 13 |