From: | Hannu Krosing <hannuk(at)google(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Robert Haas <robertmhaas(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Noah Misch <nmisch(at)google(dot)com> |
Subject: | Re: DROP OWNED BY fails to clean out pg_init_privs grants |
Date: | 2024-06-20 17:41:01 |
Message-ID: | CAMT0RQRv6pCniBu5VU0r5=P7gVS7kb5KywfUH5GcKzEVwt4umQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Then maybe we should put a query / function in the release notes to
clean up the existing mess.
Thinking of it we should do it anyway, as the patch only prevents new
messiness from happening and does not fix existing issues.
I could share a query to update the pg_init_privs with non-existent
role to replace it with the owner of the object if we figure out a
correct place to publish it.
---
Hannu
On Thu, Jun 20, 2024 at 5:35 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Hannu Krosing <hannuk(at)google(dot)com> writes:
> > Is there anything that could be back-patched with reasonable effort ?
>
> Afraid not. The whole thing is dependent on pg_shdepend entries
> that won't exist in older branches.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2024-06-20 17:43:06 | Re: DROP OWNED BY fails to clean out pg_init_privs grants |
Previous Message | David E. Wheeler | 2024-06-20 17:34:11 | Re: call for applications: mentoring program for code contributors |