On 5 December 2012 11:16, Kohei KaiGai <kai...@kaigai.gr.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
