Re: Problem getting plpgsql to choose the right query plan - Mailing list pgsql-general

From Niklas Johansson
Subject Re: Problem getting plpgsql to choose the right query plan
Date
Msg-id 0A3909E6-6D27-40D7-9AF0-380D1A2BC20C@tele2.se
Whole thread Raw
In response to Problem getting plpgsql to choose the right query plan  ("Helge Elvik" <helge.elvik@gispartner.no>)
List pgsql-general
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





pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Wal -long transaction
Next
From: Tom Lane
Date:
Subject: Re: Wal -long transaction