On 12/07/12 00:07, Tom Lane wrote:
> Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> writes:
>> The issue occurs when you have server-side prepared queries enabled, and
>> then change the search_path parameter after creating a prepared query.
>> Future executions of that query still seem to be using the original
>> search_path.
>
> This behavior is intentional.
In that case, the error lies with the Perl libraries that automatically
prepare and cache queries, but do not include the search_path in the
cache keys.
I'll bring it up with them.
thanks for your advice,
Toby