Toby Corkindale <toby.corkindale@strategicdata.com.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.
regards, tom lane