From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
Cc: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Major Feature Interactions |
Date: | 2007-03-13 15:45:17 |
Message-ID: | 2730.1173800717@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Merlin Moncure" <mmoncure(at)gmail(dot)com> writes:
> What about the interaction of plan invalidation and the security
> problems with 'security definer'? I am especially curious if pl
> functions will no longer regenerate their plans with each session for
> 8.3. Is that going to be the case? It wasn't completely clear from
> the related discussions AFAICT.
No, there's no intention of caching plans across sessions.
I'm intending to build some infrastructure in namespace.c to support
a stack of "override" search_path values, and then tweak plancache.c
to override search_path during a replan. (It has to be a stack because
nested replan events are entirely possible.) I think this
infrastructure will also work for attaching search paths to functions;
but we still lack an agreed design spec for how that should look to the
user.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Ledford | 2007-03-13 16:20:25 | Daylight Saving Time question PostgreSQL 8.1.4 |
Previous Message | Mario Weilguni | 2007-03-13 15:42:35 | Re: Bug in UTF8-Validation Code? |