From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate
Date: Wed, 9 Dec 2020 09:59:32 -0700
Message-ID: <2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com> (raw)
In-Reply-To: <154608A6-0F38-4BE8-B3F4-3E3308691F91@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>
> On Dec 9, 2020, at 7:06 AM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
>
>> On Dec 8, 2020, at 12:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> There is probably an entry in pg_default_acl that is causing this.
>> You could likely just manually remove that.
>
> I'll give it a go.
>
> But there's nothing in pg_default_acl with defaclnamespace matching oid of pg_catalog in pg_namespace. There were some erroneous entries for namespace public, which I've deleted. But I don't have a lot of confidence about that being the problem.
Nope, deleting the ACLs for public didn't help. I'm going to start stripping things down--dropping schemas, or maybe the whole db--and see if it persists.
Any other suggestions? What could possibly be triggering this GRANT?
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: scott_ribe@elevated-dev.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate
In-Reply-To: <2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com>
* 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