On 12 March 2012 16:16, Tom Lane wrote:
Robert Haas <robertmhaas@gmail.com> writes:
in
8.4.9
demonstrate
should handle it better, but I'm not sure how hard that would be to
implement.plpgsql intentionally caches the plan for the query as it was built with
the original search_path. There's been talk of adjusting that behavior
but I'm worried that we might break as many cases as we fix ...
Robert Haas <robertmhaas@gmail.com> writes:
On Mon, Mar 5, 2012 at 6:52 AM, wrote:
I found some unexpected behaviour when changing the schema search path
I found some unexpected behaviour when changing the schema search path
combination with plpgsql functions (may be true for other function types
too, did not check). This occurs both in 9.1.2 (on Fedora, 64 bit) and
too, did not check). This occurs both in 9.1.2 (on Fedora, 64 bit) and
(Centos 6, 32 bit). I created a small example run with psql, to
this.
I have a vague feeling this is a known issue. It sure seems like weshould handle it better, but I'm not sure how hard that would be to
implement.
the original search_path. There's been talk of adjusting that behavior
but I'm worried that we might break as many cases as we fix ...
connection, the "original search_path" is thus the search path that the
function happened to run in for the first time with the current database
connection.
--
René van Paassen | ______o____/_| Rene.vanPaassen@gmail.com
<[___\_\_-----< t: +31 15 2628685
o' mobile: +31 6 39846891
