On Friday 30 March 2007 16:34 Dave Dutcher wrote: > > From: pgsql-performance-owner@xxxxxxxxxxxxxx > > [mailto:pgsql-performance-owner@xxxxxxxxxxxxxx] On Behalf Of > > Vincenzo Romano > > > > Is there any "workaround"? > > > > In my opinion the later the query planner decisions are taken the more > > effective they can be. > > It could be an option for the function (body) to delay any > > query planner > > decision. > > I think a possible workaround is to use a plpgsql function and the execute > statement. The docs will have more info. > > Dave Aye sir. It works. There's not much details into the documentation but the real point is that the execute command of the PLPg/SQL actually says the DB to delay the query planning process as late as possible, I have also managed to build search functions at runtime using the execute command with a dynamically built text variable. Complex, error prone but really fast. -- Vincenzo Romano ---- Maybe Computers will never become as intelligent as Humans. For sure they won't ever become so stupid. [VR-1987]
