From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate
Date: Wed, 09 Dec 2020 12:19:18 -0500
Message-ID: <3632844.1607534358@sss.pgh.pa.us> (raw)
In-Reply-To: <2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com>
References: <074FE83A-E924-4787-9E68-27EB9CE142B3@elevated-dev.com>
<3264512.1607456932@sss.pgh.pa.us>
<154608A6-0F38-4BE8-B3F4-3E3308691F91@elevated-dev.com>
<2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com>
Scott Ribe <scott_ribe@elevated-dev.com> writes:
> Any other suggestions? What could possibly be triggering this GRANT?
Ah, I'm sorry, I pointed you at the wrong catalog entirely. It's
not pg_default_acl that controls this, it's pg_init_privs. I believe
what pg_dump is doing is emitting GRANT commands that replicate
the difference between pg_pltemplate's current actual privileges and
what is shown for it in pg_init_privs. So you need to make those
two things match, in whichever way is easiest.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott_ribe@elevated-dev.com, pgsql-admin@lists.postgresql.org
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate
In-Reply-To: <3632844.1607534358@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox