Re: Same database, different query plans - Mailing list pgsql-general

From Michael Fuhr
Subject Re: Same database, different query plans
Date
Msg-id 20050818140514.GA84091@winnie.fuhr.org
Whole thread Raw
In response to Same database, different query plans  (WireSpot <wirespot@gmail.com>)
List pgsql-general
On Thu, Aug 18, 2005 at 12:03:59PM +0300, WireSpot wrote:
> The actual SELECT results (ie. non EXPLAIN) are identical in both
> cases. The indexes and so on are identical. I've done a reindexing and
> vacuuming on both of them just to be sure.
>
> As you can see, there's quite a bit of a difference between 0.3 ms and
> 398 ms, and it shows. I haven't touched the query planning options.
> Why the different planning and what can I do to fix the misguided one?

Have you run ANALYZE or VACUUM ANALYZE in both databases to update
the planner's statistics?  If you have and get the same results,
then it might be interesting to see the output of the following on
both systems:

SET enable_mergejoin TO off;
SET enable_nestloop TO on;
EXPLAIN ANALYZE SELECT ...

SET enable_mergejoin TO on;
SET enable_nestloop TO off;
EXPLAIN ANALYZE SELECT ...

--
Michael Fuhr

pgsql-general by date:

Previous
From: "Michel Bouchard"
Date:
Subject:
Next
From: "Andrus"
Date:
Subject: How to determine table schema in trigger function