| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)mail(dot)com> |
| Subject: | Re: Review of Row Level Security |
| Date: | 2013-01-02 17:31:42 |
| Message-ID: | CA+U5nMKYL4-yRuCQTGe28sid=rr+eFtZy8KEGgr_Tw+c1-Sudw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
Doubt it.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2013-01-02 17:44:39 | Re: Review of Row Level Security |
| Previous Message | Fabrízio de Royes Mello | 2013-01-02 17:26:42 | Re: Minor fix in 'clean' action of 'src/backend/Makefile' |