Re: table partitioning and access privileges - Mailing list pgsql-hackers

From Amit Langote
Subject Re: table partitioning and access privileges
Date
Msg-id CA+HiwqEkiApF9ieeHJigYTohmjmjLR5SB6-i3FbOQnLSUy8Ezg@mail.gmail.com
Whole thread Raw
In response to Re: table partitioning and access privileges  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: table partitioning and access privileges
List pgsql-hackers
On Fri, Feb 7, 2020 at 1:16 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
> On 2020/02/03 14:26, Amit Langote wrote:
> > On Mon, Feb 3, 2020 at 2:07 PM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
> >> On 2020/02/03 11:05, Amit Langote wrote:
> >>> Okay.  How about the attached?
> >>
> >> Thanks for the patches! You added the note just after the description
> >> about row level security on inherited table, but isn't it better to
> >> add it before that? Attached patch does that. Thought?
> >
> > Yeah, that might be a better flow for that paragraph.
>
> Pushed! Thanks!

Thank you.

> >>> Maybe, we should also note the LOCK TABLE exception?
> >>
> >> Yes.
> >
> > Note that, unlike TRUNCATE, LOCK TABLE exception exists in HEAD too,
> > but maybe you're aware of that.
>
> Yes, so I will review your patch getting rid of
> LOCK TABLE exception.

Attached updated patch.

Regards,
Amit

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Getting rid of some more lseek() calls
Next
From: Andres Freund
Date:
Subject: Re: Prevent pg_basebackup running as root