On Thu, 9 Jun 2005 [EMAIL PROTECTED] wrote:

> I am continously encountering an issue with query plans that changes after 
> a pg_dump / pg_restore operation has been performed.
> Have placed an export of the query, query plan etc. online at: 
> in order to ensure it's still 
> readable.

There is not a major difference in time, so pg is at least not way off 
(225ms vs. 280ms). The estimated cost is however not very related to the 
runtime (117 vs 1389).

What you have not showed is if the database is properly tuned. The output
of SHOW ALL; could help explain a lot together with info of how much
memory your computer have.

The first thing that comes to mind to me is that you probably have not 
tuned shared_buffers and effective_cache_size properly (SHOW ALL would 

/Dennis Björklund

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to