On 2 January 2013 17:19, David Fetter <david(at)fetter(dot)org> wrote:
> Would COPY be covered separately? How about TRUNCATE?
COPY == INSERT
TRUNCATE isn't covered at all since it doesn't look at rows. It has a
separate privilege that can be granted to those that need it.
> Also, is there any way to apply this to the catalog, or would that be
> too large a restructuring, given how catalog access actually works?
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: David Fetter||Date: 2013-01-02 17:44:39|
|Subject: Re: Review of Row Level Security|
|Previous:||From: Fabrízio de Royes Mello||Date: 2013-01-02 17:26:42|
|Subject: Re: Minor fix in 'clean' action of 'src/backend/Makefile'|