| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: table partitioning and access privileges |
| Date: | 2020-02-03 05:26:55 |
| Message-ID: | CA+HiwqFbwt4=KQy3S4OOqi=Pi4QywNXxfqesAkAObxjUD9okVQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 3, 2020 at 2:07 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)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.
> > 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.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-02-03 06:45:21 | Re: ERROR: subtransaction logged without previous top-level txn record |
| Previous Message | Fujii Masao | 2020-02-03 05:07:35 | Re: table partitioning and access privileges |