| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Review of Row Level Security |
| Date: | 2012-12-07 18:33:13 |
| Message-ID: | CA+U5nMJTmEazbK1UEGuPXy8s+pzOQB3M2upm3bU1W9VpfGjznA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 December 2012 11:16, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
>> * TRUNCATE works, and allows you to remove all rows of a table, even
>> ones you can't see to run a DELETE on. Er...
>>
> It was my oversight. My preference is to rewrite TRUNCATE command
> with DELETE statement in case when row-security policy is active on
> the target table.
> In this case, a NOTICE message may be helpful for users not to assume
> the table is always empty after the command.
I think the default must be to throw an ERROR, since part of the
contract with TRUNCATE is that it is fast and removes storage.
>> * Docs need work, but thats OK.
>>
> I'd like to want some help with native English speakers.
I'll help with that.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-12-07 18:39:34 | Re: Review of Row Level Security |
| Previous Message | Andres Freund | 2012-12-07 18:27:08 | Re: pg_upgrade problem with invalid indexes |