Re: Broken lock management in policy.c. - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Broken lock management in policy.c.
Date
Msg-id CAM3SWZSk+oP3qZAgHgQrMd0QLA2zQngr-1wu+XNb28L=ZkW4pg@mail.gmail.com
Whole thread Raw
In response to Re: Broken lock management in policy.c.  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Broken lock management in policy.c.  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Sun, Jan 3, 2016 at 6:41 PM, Stephen Frost <sfrost@snowman.net> wrote:
> A security defined function could be used to address that, of course. That
> could have performance implications, naturally.

True.

I would also advise only referencing a single relation within the
SELECT FOR UPDATE.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: row_security GUC does not behave as documented
Next
From: Tom Lane
Date:
Subject: Re: 9.5 BLOCKER: regrole and regnamespace and quotes