Re: Row Level Security UPDATE Confusion

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Rod Taylor <rod(dot)taylor(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>
Subject: Re: Row Level Security UPDATE Confusion
Date: 2017-04-13 19:54:09
Message-ID: CA+TgmoYMKHwMu-Rt635H4cZZn3VMp_jUTa34pg0FQpeaBM8VAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 6, 2017 at 4:05 PM, Rod Taylor <rod(dot)taylor(at)gmail(dot)com> wrote:
> I'm a little confused on why a SELECT policy fires against the NEW record
> for an UPDATE when using multiple FOR policies. The ALL policy doesn't seem
> to have that restriction.

My guess is that you have found a bug.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-04-13 20:03:38 Re: pg_upgrade vs extension upgrades
Previous Message Magnus Hagander 2017-04-13 19:48:55 Re: pg_upgrade vs extension upgrades