| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Thomas Kellerer <shammat(at)gmx(dot)net> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_upgrade issue upgrading 10 -> 13 |
| Date: | 2020-10-01 15:43:52 |
| Message-ID: | 20201001154352.GA15909@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Oct 1, 2020 at 05:28:53PM +0200, Thomas Kellerer wrote:
>
>
> Sean Brown schrieb am 01.10.2020 um 16:51:
> > 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”;
> >
> > Is there a way to deal with this that doesn’t include dropping the
> > source table?
> >
>
> Does revoking the privilege before running pg_upgrade help?
>
> So in the v10 database:
>
> revoke select on pg_catalog.pg_pltemplate from appuser;
Yeah, there must be a reference to pg_catalog.pg_pltemplate somewhere
that was missed. I think a simple dump/restore would also error on the
restore, but a normal restore might ignore the error, while pg_upgrade
will not.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-10-01 16:03:31 | Re: pg_upgrade issue upgrading 10 -> 13 |
| Previous Message | Thomas Kellerer | 2020-10-01 15:28:53 | Re: pg_upgrade issue upgrading 10 -> 13 |