Horton

Re: Review of Row Level Security

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndQuadrant.com>
To: David Fetter <david@fetter.org>
Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>, PostgreSQL-development <pgsql-hackers@postgresql.org>, Stephen Frost <sfrost@snowman.net>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Kevin Grittner <kgrittn@mail.com>
Date: 2013-01-02T17:31:42Z
Lists: pgsql-hackers 
On 2 January 2013 17:19, David Fetter <david@fetter.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?

Doubt it.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services