Re: Review of Row Level Security

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Kevin Grittner <kgrittn(at)mail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Review of Row Level Security
Date: 2012-12-21 09:29:38
Message-ID: CAEZATCWveQo9ABqUDE++n6aFzQav0orxH1Y3T2cB11rL861egw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 21 December 2012 08:56, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> It's unreasonable for people to demand a feature yet provide no
> guidance to the person trying (hard) to provide that feature in a
> sensible way. If people genuinely believe case (2) is worth pursuing,
> additional work and input is needed so that KaiGai can make changes in
> time for the 9.3 deadline. Please read what KaiGai has said and
> respond. Since there are so many people reading this thread and
> wanting (2), that seems reasonable to expect.
>
> What I have proposed is that I work on the review for case (1) and
> then if we solve (2) that can go in also. I don't think its reasonable
> to reject the whole feature because of unresolved difficulties around
> one use case, which is what will happen if this is seen as merely a
> debate about defaults.
>

One comment on the code itself -- I think it needs some locking of
rows from the subquery to ensure correct concurrency behaviour when
there are multiple transactions doing updates at the same time.

Regards,
Dean

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2012-12-21 10:04:36 Re: Review of Row Level Security
Previous Message Simon Riggs 2012-12-21 08:56:07 Re: Review of Row Level Security