Excerpts from Tom Lane's message of jue dic 22 19:09:54 -0300 2011:
>
> Alvaro Herrera writes:
> > Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011:
> >> Robert Haas writes:
> >>> Add a security_barrier option for views.
>
> >> Where's the catversion bump for having broken st
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011:
>> Robert Haas writes:
>>> Add a security_barrier option for views.
>> Where's the catversion bump for having broken stored rules/views?
> I'm starting to wonder if we should have a git hook of some sor
On Thu, Dec 22, 2011 at 4:17 PM, Robert Haas wrote:
> Add a security_barrier option for views.
>
you have some docs typos here, for the rest: cool.
doc/src/sgml/ref/create_view.sgml
"""
+ This clause specifies optional parameters for a view; currently, the
+ only suppored parameter nam
Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011:
> Robert Haas writes:
> > Add a security_barrier option for views.
>
> Where's the catversion bump for having broken stored rules/views?
I'm starting to wonder if we should have a git hook of some sort to
check for this ...
--
Robert Haas writes:
> Add a security_barrier option for views.
Where's the catversion bump for having broken stored rules/views?
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://ww
Add a security_barrier option for views.
When a view is marked as a security barrier, it will not be pulled up
into the containing query, and no quals will be pushed down into it,
so that no function or operator chosen by the user can be applied to
rows not exposed by the view. Views not configur
