Re: copy.c handling for RLS is insecure - Mailing list pgsql-hackers

From Andres Freund
Subject Re: copy.c handling for RLS is insecure
Date
Msg-id 20150709084148.GU10242@alap3.anarazel.de
Whole thread Raw
In response to Re: copy.c handling for RLS is insecure  (Noah Misch <noah@leadboat.com>)
Responses Re: copy.c handling for RLS is insecure  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On 2015-07-09 01:28:28 -0400, Noah Misch wrote:
> > - Keep the OID check, shouldn't hurt to have it
> 
> What benefit is left?

A bit of defense in depth. We execute user defined code in COPY
(e.g. BEFORE triggers). That user defined code could very well replace
the relation. Now I think right now that'd happen late enough, so the
second lookup already happened. But a bit more robust defense against
that sounds good to me.



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Further issues with jsonb semantics, documentation
Next
From: David Rowley
Date:
Subject: Re: Sharing aggregate states between different aggregate functions