From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "Dives, Chloe" <Chloe(dot)Dives(at)gam(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Privilege error with c functions during postgresql upgrade from 11 -> 13 |
Date: | 2022-04-28 16:52:51 |
Message-ID: | a7b43839-e8a9-7df6-4aeb-6fb5e58fab92@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/28/22 02:08, Dives, Chloe wrote:
> Thanks for your reply. I am using pg_upgrade to do the upgrade
In the Postgres 11 instance using psql what does:
\df+ bt_index_check
return.
In particular under the Access privileges column.
Also the output of:
\du
Going back to your original post, someone who is more familiar with
pg_upgrade maybe can explain:
Command was: SELECT pg_catalog.binary_upgrade_set_record_init_privs(true);
REVOKE ALL ON FUNCTION "public"."bt_index_check"("index" "regclass")
FROM PUBLIC;
REVOKE ALL ON FUNCTION "public"."bt_index_check"("index" "regclass")
FROM "rolename1";
SET SESSION AUTHORIZATION "16416";
GRANT ALL ON FUNCTION "public"."bt_index_check"("index" "regclass") TO
"16416";
RESET SESSION AUTHORIZATION;
SELECT pg_catalog.binary_upgrade_set_record_init_privs(false);
REVOKE ALL ON FUNCTION "public"."bt_index_check"("index" "regclass")
FROM "16416";
In other words why the role 16416 was GRANTed ALL then REVOKEd ALL on
the function?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | JORGE MALDONADO | 2022-04-28 16:57:31 | Re: Backing up a DB excluding certain tables |
Previous Message | Tom Lane | 2022-04-28 16:43:17 | Re: Backing up a DB excluding certain tables |