| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Floris Van Nee <florisvannee(at)optiver(dot)com>, Kirill Reshke <reshke(at)double(dot)cloud>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_init_privs corruption. |
| Date: | 2023-04-12 01:48:12 |
| Message-ID: | CAM-w4HOnLNrpNtJTYqhY32O=-LW0XHhxCb-9SKR8MSuLsXct6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 17 Feb 2023 at 15:38, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Hmm, so Stephen was opining that the extension's objects shouldn't
> have gotten these privs attached in the first place. I'm not
> quite convinced about that one way or the other, but if you buy it
> then maybe this situation is unreachable once we fix that.
Well pg_dump might still have to deal with it even if it's unreachable
in new databases (or rather schemas with extensions newly added... it
might be hard to explain what cases are affected).
Alternately it'll be a note at the top of every point release pointing
at a note explaining how to run a script to fix your schemas.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2023-04-12 01:59:22 | Re: Protecting allocator headers with Valgrind |
| Previous Message | Stephen Frost | 2023-04-12 01:45:13 | Re: longfin missing gssapi_ext.h |