| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marcus Müller <m(dot)mueller(at)schwarz-infosysteme(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_upgrade from PostgreSQL 12.4 to PostgreSQL 13.2 on Windows 10 failes because of missing function pg_catalog.ascii_to_mic |
| Date: | 2021-03-10 15:16:00 |
| Message-ID: | 2088847.1615389360@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?iso-8859-1?Q?Marcus_M=FCller?= <m(dot)mueller(at)schwarz-infosysteme(dot)de> writes:
> pg_upgrade should actually correctly handle features that no longer exist in
> a new version. This seems like a bug.
> 2021-03-10 10:37:07.199 CET [18868] FEHLER: Funktion
> pg_catalog.ascii_to_mic(integer, integer, cstring, internal, integer)
> existiert nicht
> 2021-03-10 10:37:07.199 CET [18868] ANWEISUNG: GRANT ALL ON FUNCTION
> "pg_catalog"."ascii_to_mic"(integer, integer, "cstring", "internal",
> integer) TO "wwsuser";
Yeah, that's a known issue, but fixing it is harder than you might think
--- people have been poking at a fix for some time without success.
There's no good place to locate knowledge about things having gone
away.
Since I can see no actual reason to grant nondefault permissions on an
encoding conversion function, I'd suggest just revoking those in the
source DB before upgrading.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2021-03-10 15:17:07 | Re: COPY TO (query) allows no function arguments |
| Previous Message | 2021-03-10 14:48:34 | COPY TO (query) allows no function arguments |