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

In response to

• Re: Review of Row Level Security at 2012-12-05 11:16:30 from Kohei KaiGai

Responses

• Re: Review of Row Level Security at 2012-12-09 06:08:31 from Kohei KaiGai

pgsql-hackers by date

Next:	From: Simon Riggs	Date: 2012-12-07 18:39:34
	Subject: Re: Review of Row Level Security
Previous:	From: Andres Freund	Date: 2012-12-07 18:27:08
	Subject: Re: pg_upgrade problem with invalid indexes