Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows - Mailing list pgsql-hackers

From Paul A Jungwirth
Subject Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows
Date
Msg-id CA+renyWYcQ=Yc1zQJ2UzLDF2cdHBHto-dRHw9s9EAA111ApEqQ@mail.gmail.com
Whole thread
In response to Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows  (Paul A Jungwirth <pj@illuminatedcomputing.com>)
Responses Re: Fix RLS checks for UPDATE/DELETE FOR PORTION OF leftover rows
List pgsql-hackers
> Is this the right way to do these checks? I'll try to look into it a
> bit more today, but does this cause problems when an UPDATE *doesn't*
> create leftovers?

I did some extra testing but couldn't find any problems. I looked at
INSERT policies when FOR PORTION OF exactly matches a row's bounds (so
the row is updated but there are no leftovers), and also INSERT
policies that include sublinks.

> We should update the documentation as well. I think it should point
> out the contrast between ACLs and RLS here.

Here is a v2 with a couple lines of documentation added.

Yours,

-- 
Paul              ~{:-)
pj@illuminatedcomputing.com

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: satisfies_hash_partition crash
Next
From: surya poondla
Date:
Subject: Re: psql: Fix \df tab completion for procedures