Re: Privileges on PUBLICATION - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Privileges on PUBLICATION
Date
Msg-id CAA4eK1KuuPoQQFmZgAagxAkLTvevgsBY8hUiWcfrkiQMCP8wqg@mail.gmail.com
Whole thread Raw
In response to Re: Privileges on PUBLICATION  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Thu, Nov 3, 2022 at 9:19 PM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
>
> On 03.11.22 01:43, Antonin Houska wrote:
> > Peter Eisentraut <peter.eisentraut@enterprisedb.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.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Privileges on PUBLICATION
Next
From: Ian Lawrence Barwick
Date:
Subject: Re: [PATCH] pgbench: add multiconnect option