| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: 12 to 13 migration, the privs error with pg_pltemplate |
| Date: | 2020-12-09 16:59:32 |
| Message-ID: | 2BD26D52-19B8-42CD-860D-B9AE21AF5C61@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Dec 9, 2020, at 7:06 AM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
>
>> On Dec 8, 2020, at 12:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-12-09 17:19:18 | Re: 12 to 13 migration, the privs error with pg_pltemplate |
| Previous Message | Stephen Frost | 2020-12-09 16:30:50 | Re: LDAP and roles |