> From: pgsql-performance-owner(at)postgresql(dot)org
> [mailto:pgsql-performance-owner(at)postgresql(dot)org] 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
I think a possible workaround is to use a plpgsql function and the execute
statement. The docs will have more info.
In response to
pgsql-performance by date
|Next:||From: Tom Lane||Date: 2007-03-30 16:13:00|
|Subject: Re: Wrong plan sequential scan instead of an index one |
|Previous:||From: Dimitri||Date: 2007-03-30 14:25:16|
|Subject: Re: Shared buffers, db transactions commited, and write IO on Solaris|