> It's planned once per query. There's been some talk of building a
> cross-query plan cache for SQL functions, like plpgsql has, but
> nothing done yet.
Several weeks ago I posted a note about a plpgsql function that fails
if an index that existed when it was created is subsequently dropped.
(I think this should be considered a bug, the existence or nonexistence
of indexes should affect performance, not whether queries fail.)
Would a cross-query plan cache for SQL functions create similar problems?
--
Mike Nolan
