Re: 9.2: Describing a security barrier view in psql - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: 9.2: Describing a security barrier view in psql
Date
Msg-id CABUevEwXoFzrcLUwb=E+nE4SDL5om-o36_1tJyRgMCQQsLPRUQ@mail.gmail.com
Whole thread Raw
In response to Re: 9.2: Describing a security barrier view in psql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Sep 3, 2012 at 3:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dean Rasheed <dean.a.rasheed@gmail.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 HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 9.2: Describing a security barrier view in psql
Next
From: Bruce Momjian
Date:
Subject: Re: Yet another failure mode in pg_upgrade