Re: wrong search_path being used

Hi Tom,

Why not implement a session/database option to use (or not) the replanning
of such functions. This would allow existing PG clusters to behave as they
historically did, and would simultaneously allow users who want to have
benefit of dynamically changing "search_path" inside a function to obtain
the expected result.

IMO, the query plan cache is a huge mistake, if it couldn't be disabled (in
another way than using EXECUTE). Perhaps based on the volatility of the
function ?
I intensively use schemas in a "heavy" PG database (understand
business-oriented logic db) and I'm today blocked by not being able to
select schemas in functions called several times in a session, leading to
wrong results. If performance is a good thing, getting the expected result
is primordial.

Lastly, is it planned to resolve this bug quickly ?

Thanks for your attention - and your involvement in PG project ;-)

--
View this message in context: http://postgresql.1045698.n5.nabble.com/wrong-search-path-being-used-tp5739027p5752394.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.