"Subbiah Stalin-XCGF84" <SSubbiah@Motorola.com> wrote:
> Not sure what's wrong in below execution plan but at times the query
> runs for 5 minutes to complete and after a while it runs within a
> second or two.
The plan doesn't look entirely unreasonable for the given query,
although it's hard to be sure of that without seeing the table
definitions. Given the plan, the times look to be about what I'd
expect for uncached and cached timings. (That is, on subsequent runs,
the data is sitting in RAM, so you don't need to access the hard
drives.)
If the initial run time is unacceptable for your environment, and
there's no way to have the cached "primed" when it matters, please
give more details on your table layouts, and perhaps someone can make
a useful suggestion.
> Pg 8.2.7, Sol10.
One quick suggestion -- upgrade your PostgreSQL version if at all
possible. The latest bug-fix version of 8.2 is currently 8.2.13, and
there are significant performance improvements in 8.3 and the newly
released 8.4.
-Kevin
