Re: pgsql: Add a security_barrier option for views.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Add a security_barrier option for views.
Дата
Msg-id 29875.1324591794@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Add a security_barrier option for views.  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: pgsql: Add a security_barrier option for views.  (Alvaro Herrera <alvherre@commandprompt.com>)
Список 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 по дате отправления:

Предыдущее
От: Jaime Casanova
Дата:
Сообщение: Re: pgsql: Add a security_barrier option for views.
Следующее
От: Robert Haas
Дата:
Сообщение: pgsql: Catversion bump for commit 0e4611c0234d89e288a53351f775c59522bae