Re: [v9.3] Row-Level Security - Mailing list pgsql-hackers

From Florian Pflug
Subject Re: [v9.3] Row-Level Security
Date
Msg-id DFBBD1D7-68C0-4364-BF02-AFA56BEA8AF6@phlo.org
Whole thread Raw
In response to Re: [v9.3] Row-Level Security  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Responses Re: [v9.3] Row-Level Security  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
List pgsql-hackers
On Jun27, 2012, at 15:07 , Kohei KaiGai wrote:
> Probably, PlannedStmt->invalItems allows to handle invalidation of
> plan-cache without big code changes. I'll try to put a flag of user-id
> to track the query plan with RLS assumed, or InvalidOid if no RLS
> was applied in this plan.
> I'll investigate the implementation for more details.
> 
> Do we have any other scenario that run a query plan under different
> user privilege rather than planner stage?

Hm, what happens if a SECURITY DEFINER functions returns a refcursor?

Actually, I wonder how we handle that today. If the executor is
responsible for permission checks, that wouldn't we apply the calling
function's privilege level in that case, at least of the cursor isn't
fetched from in the SECURITY DEFINER function? If I find some time,
I'll check...

best regards,
Florian Pflug



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Regarding WAL Format Changes
Next
From: Andres Freund
Date:
Subject: Re: [COMMITTERS] pgsql: Move WAL continuation record information to WAL page header.