Re: Problem getting plpgsql to choose the right query plan

On 13 mar 2006, at 11.35, Helge Elvik wrote:
> Is there any way for me to force plpgsql not to use a cached query
> plan, but instead figure out what’s best based on the LIKE-string
> that actually get passed to the function?
You can build the query as a string and EXECUTE it. This will force a
new plan to be prepared.

http://www.postgresql.org/docs/8.1/interactive/plpgsql-
statements.html#PLPGSQL-STATEMENTS-EXECUTING-DYN

Sincerely,

Niklas Johansson