| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
| Cc: | Noah Misch <noah(at)2ndquadrant(dot)com>, Kohei Kaigai <Kohei(dot)Kaigai(at)emea(dot)nec(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [v9.2] Fix leaky-view problem, part 1 |
| Date: | 2011-07-02 19:41:45 |
| Message-ID: | CA+Tgmobb1-Fgf6ihZVr74OEobaaoQoVMK3JhFH-y8BLX-=HM-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 2, 2011 at 1:54 PM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> BTW, regarding to the statement support for security barrier views,
> the following syntax might be more consistent with existing ones:
> CREATE VIEW view_name WITH ( param [=value]) AS query ... ;
> rather than
> CREATE SECURITY VIEW view_name AS query ...;
>
> Any comments?
I think I mildly prefer CREATE SECURITY VIEW to the parameter syntax
in this case, but I don't hate the other one.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-07-02 19:45:03 | Re: Deriving release notes from git commit messages |
| Previous Message | Tom Lane | 2011-07-02 18:46:10 | Re: Optimizing pg_trgm makesign() (was Re: WIP: Fast GiST index build) |