Re: [v9.2] Fix leaky-view problem, part 1 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [v9.2] Fix leaky-view problem, part 1
Date
Msg-id CA+Tgmobb1-Fgf6ihZVr74OEobaaoQoVMK3JhFH-y8BLX-=HM-w@mail.gmail.com
Whole thread Raw
In response to Re: [v9.2] Fix leaky-view problem, part 1  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Responses Re: [v9.2] Fix leaky-view problem, part 1
List pgsql-hackers
On Sat, Jul 2, 2011 at 1:54 PM, Kohei KaiGai <kaigai@kaigai.gr.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Optimizing pg_trgm makesign() (was Re: WIP: Fast GiST index build)
Next
From: Robert Haas
Date:
Subject: Re: Deriving release notes from git commit messages