Re: pgsql: Add a security_barrier option for views. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Add a security_barrier option for views.
Date
Msg-id 29875.1324591794@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Add a security_barrier option for views.  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pgsql: Add a security_barrier option for views.  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-committers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011:
>> Robert Haas <rhaas@postgresql.org> 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 ...

Dunno, how would you automate that?

My rule of thumb is that touching either src/include/catalog/* or
readfuncs.c probably means you need a catversion bump.  It's the
"probably" that's a problem for automated enforcement.  I don't
want unnecessary catversion bumps happening just because some tool
is preventing a commit.

            regards, tom lane

pgsql-committers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: pgsql: Add a security_barrier option for views.
Next
From: Robert Haas
Date:
Subject: pgsql: Catversion bump for commit 0e4611c0234d89e288a53351f775c59522bae