From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Greg Smith <greg(dot)smith(at)crunchydatasolutions(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP patch (v2) for updatable security barrier views |
Date: | 2014-04-13 04:52:12 |
Message-ID: | 20140413045211.GM2556@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg,
* Gregory Smith (gregsmithpgsql(at)gmail(dot)com) wrote:
> Now that Tom has given some guidance on the row locking weirdness,
> maybe it's time for me to start updating those into make check form.
If you have time, that'd certainly be helpful.
> The documentation has been in a similar holding pattern. I have
> lots of resources to help document what does and doesn't work here
> to the quality expected in the manual. I just need a little more
> confidence about which feature set is commit worthy. The
> documentation that makes sense is very different if only updatable
> security barrier views is committed.
Guess I see that a bit differently- the two features, while they might
be able to be used together, should both be documented appropriately and
at the level that each can be used independently. I'm not sure that
documentation about how to build RLS on top of updatable security
barrier views w/o actual RLS support being in PG would be something we'd
want to include in the PG documentation, which I guess is what you're
getting at here.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2014-04-13 04:59:28 | Patch to fix a couple of compiler warnings from 80a5cf64 |
Previous Message | Amit Kapila | 2014-04-13 04:51:37 | Re: PostgreSQL in Windows console and Ctrl-C |