Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Add a security_barrier option for views.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Add a security_barrier option for views.
Date: 2011-12-22 22:09:54
Message-ID: 29875.1324591794@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Excerpts from Tom Lane's message of jue dic 22 18:39:18 -0300 2011:
>> Robert Haas <rhaas(at)postgresql(dot)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

In response to

Responses

pgsql-committers by date

Next:From: Robert HaasDate: 2011-12-22 22:25:52
Subject: pgsql: Catversion bump for commit0e4611c0234d89e288a53351f775c59522bae
Previous:From: Jaime CasanovaDate: 2011-12-22 22:01:42
Subject: Re: pgsql: Add a security_barrier option for views.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group