Re: Privileges on PUBLICATION

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Antonin Houska <ah@cybertec.at>, Euler Taveira <euler@eulerto.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-11-04T04:31:02Z
Lists: 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.



Commits

  1. Refactor ExecGrant_*() functions

  2. doc: Add note about lack of publication privileges