Re: 9.2: Describing a security barrier view in psql

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 9.2: Describing a security barrier view in psql
Date: 2012-09-03 13:51:07
Message-ID: CABUevEwXoFzrcLUwb=E+nE4SDL5om-o36_1tJyRgMCQQsLPRUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 3, 2012 at 3:48 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> writes:
>> Unless I'm missing something, it is not possible in psql to tell
>> whether a view has the security_barrier option. I think that this is
>> something that ought to be possible from psql, otherwise the new
>> feature is not visible.
>
>> This patch displays any reloptions for a view at the end, if \d+ is
>> used, in the same way as for tables.
>
>> Sorry if this is too late for 9.2. I really only just noticed this,
>> despite playing with security barrier views for a while.
>
> Seems to me we should include this into 9.2, since the security_barrier
> feature exists there. It's not quite too late. Any objections?

+1, I was about to suggest that myself.

Haven't reviewed the code, I'm talking about the principle. I think it
can almost be considered a bugfix for the security_barrier feature.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2012-09-03 13:52:22 Re: Yet another failure mode in pg_upgrade
Previous Message Tom Lane 2012-09-03 13:48:01 Re: 9.2: Describing a security barrier view in psql