Re: pg_upgrade --check doesn't check pg_pltemplate modifications - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_upgrade --check doesn't check pg_pltemplate modifications
Date
Msg-id 3704260.1642351394@sss.pgh.pa.us
Whole thread Raw
In response to pg_upgrade --check doesn't check pg_pltemplate modifications  (Tomas Barton <barton.tomas@gmail.com>)
List pgsql-bugs
Tomas Barton <barton.tomas@gmail.com> writes:
> Any non-default GRANT/REVOKE like these:

> REVOKE SELECT ON TABLE "pg_catalog"."pg_pltemplate" FROM PUBLIC;
> GRANT SELECT ON TABLE "pg_catalog"."pg_pltemplate" TO "reader";

Uh ... why would you do that?  It seems only academically
different from randomly deleting some catalog entries.

> would break the upgrade process, even though the pg_upgrade --check says:
> *Clusters are compatible*

pg_upgrade has never promised to detect every possible problem.
Considering that pg_pltemplate is gone entirely in v13 and up,
I doubt we're going to want to invest a lot of effort here.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Mario Emmenlauer
Date:
Subject: Re: BUG #17365: Error: redefinition of 'stat' in win32_port.h when including postgres.h
Next
From: Tom Lane
Date:
Subject: Re: BUG #17363: 14 regression: "could not identify a hash function for type record" in a nested record in sublink