| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Antonin Houska <ah(at)cybertec(dot)at>, Euler Taveira <euler(at)eulerto(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Privileges on PUBLICATION |
| Date: | 2022-11-04 04:31:02 |
| Message-ID: | CAA4eK1KuuPoQQFmZgAagxAkLTvevgsBY8hUiWcfrkiQMCP8wqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 3, 2022 at 9:19 PM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> On 03.11.22 01:43, Antonin Houska wrote:
> > Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
> >
> >> The CF entry is about privileges on publications. Please rebase that patch
> >> and repost it so that the CF app and the CF bot are up to date.
> >
> > The rebased patch (with regression tests added) is attached here.
>
> Some preliminary discussion:
>
> What is the upgrade strategy? I suppose the options are either that
> publications have a default acl that makes them publicly accessible,
> thus preserving the existing behavior by default, or pg_dump would need
> to create additional GRANT statements when upgrading from pre-PG16.
>
I think making them publicly accessible is a better option.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lawrence Barwick | 2022-11-04 04:39:48 | Re: [PATCH] pgbench: add multiconnect option |
| Previous Message | Amit Kapila | 2022-11-04 04:29:43 | Re: Privileges on PUBLICATION |