Re: Flexible permissions for REFRESH MATERIALIZED VIEW - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: Flexible permissions for REFRESH MATERIALIZED VIEW
Date
Msg-id CA+q6zcXh-sXg=F5EnO5EHuYZF=qd35vW_cCqOvpzrWEscj=KDQ@mail.gmail.com
Whole thread Raw
In response to Re: Flexible permissions for REFRESH MATERIALIZED VIEW  (Dmitry Dolgov <9erthalion6@gmail.com>)
List pgsql-hackers
On Mon, Nov 5, 2018 at 4:19 PM Dmitry Dolgov <9erthalion6@gmail.com> wrote:
>
> This patch went through the last two commit fests without any noticeable
> activity. As far as I can see, judging from the discussion, there isn't a
> single opinion everyone would agree with, except that simply introducing a new
> permission is probably not enough and we need to address how to do this
> in an extendable way.
>
> > On Sun, 18 Mar 2018 at 22:05, Isaac Morland <isaac.morland@gmail.com> wrote:
> >
> > Right now I'm really looking for whether anybody observes any problems with
> > the basic idea. If it's considered to be at least in principle a good idea
> > then I'll go and make a more complete patch.
>
> There were at least two options suggested about how to address the questions
> from the discussion (widening AclMode and introducing another type similar to
> aclitem, but more flexible, to store an "extended" permissions). Maybe the
> constructive approach here would be to try them out and propose a draft
> implementation for one of them?

Due to lack of response I'm marking it as "Returned with feedback". Feel free
to resubmit a new version though.


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pg_config wrongly marked as not parallel safe?
Next
From: Tom Lane
Date:
Subject: Re: pg_config wrongly marked as not parallel safe?