On Mon, Jul 2, 2012 at 10:55 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> The attached patch is delivered from the discussion around row-level
> access control feature. A problem Florian pointed out is refcursor
> declared in security definer function. Even though all the permission
> checks are applied based on privilege of the owner of security-definer
> function in case when it tries to define a cursor bound to a particular
> query, it shall be executed under the credential of executor.
> In the result, "current_user" or "has_table_privilege()" will return
> unexpected result, even if it would be used in as a part of security
> policy for each row.

Why not just save and restore the user ID and security context
unconditionally, instead of doing this kind of dance?

+               if (portal->userId != GetUserId())
+                       SetUserIdAndSecContext(portal->userId, portal->secCo
+               else
+                       saveUserId = InvalidOid;

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

In response to

• User-Id Tracking when Portal was started at 2012-07-02 14:55:39 from Kohei KaiGai

Responses

• Re: User-Id Tracking when Portal was started at 2012-07-03 15:33:09 from Kohei KaiGai

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2012-07-03 15:02:15
	Subject: Re: [PATCH 08/16] Introduce the ApplyCache module which can reassemble transactions from a stream of interspersed changes
Previous:	From: Jeff Davis	Date: 2012-07-03 14:26:08
	Subject: Re: SP-GiST for ranges based on 2d-mapping and quad-tree