Re: 12 to 13 migration, the privs error with pg_pltemplate - Mailing list pgsql-admin

From Scott Ribe
Subject Re: 12 to 13 migration, the privs error with pg_pltemplate
Date
Msg-id 2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com
Whole thread Raw
In response to Re: 12 to 13 migration, the privs error with pg_pltemplate  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: 12 to 13 migration, the privs error with pg_pltemplate  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
> 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
someerroneous entries for namespace public, which I've deleted. But I don't have a lot of confidence about that being
theproblem. 

Nope, deleting the ACLs for public didn't help. I'm going to start stripping things down--dropping schemas, or maybe
thewhole db--and see if it persists. 

Any other suggestions? What could possibly be triggering this GRANT?






pgsql-admin by date:

Previous
From: Stephen Frost
Date:
Subject: Re: LDAP and roles
Next
From: Tom Lane
Date:
Subject: Re: 12 to 13 migration, the privs error with pg_pltemplate