Re: stange optimizer results

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: "Peter T(dot) Brown" <peter(at)memeticsystems(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: stange optimizer results
Date: 2002-11-21 18:35:37
Message-ID: 20021121103424.X96861-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On Thu, 21 Nov 2002, Stephan Szabo wrote:

> On 21 Nov 2002, Peter T. Brown wrote:
>
> > Hello--
> >
> > Attached is a file containing two SQL queries. The first take
> > prohibitively long to complete because, according to EXPLAIN, it ignore
> > two very important indexes. The second SQL query seems almost identical
> > to the first but runs very fast because, according to EXPLAIN, it does
> > uses all the indexes appropriately.
> >
> > Can someone please explain to me what the difference is here? Or if
> > there is something I can do with my indexes to make the first query run
> > like the second?
>
> It doesn't take into account that in general a=b, b=constant implies
> a=constant.
>
> Perhaps if you used explicit join syntax for visitor joining
> visitorextra it might help. Like doing:
> FROM visitor inner join visitorextra on (...)
> left outer join ...

Sent this too quickly. It probably won't make it use an index on
vistorextra, but it may lower the number of expected rows that it's going
to be left outer joining so that a nested loop and index scan makes sense.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message george young 2002-11-21 18:50:36 Re: vacuum full
Previous Message Stephan Szabo 2002-11-21 18:34:14 Re: stange optimizer results