Skip site navigation (1) Skip section navigation (2)

Re: Forcing filter/join order?

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Forcing filter/join order?
Date: 2004-02-19 00:56:22
Message-ID: 20040218165410.G36125@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Wed, 18 Feb 2004, Josh Berkus wrote:

> The planner can't, or doesn't want to, use an index on (event_date,
> (event_date + duration)) where the first column is an ascending sort and the
> second a descending sort.    So I've coded a workaround that's quite
> inelegant but does get the correct results in 0.3 seconds (as opposed to the
> 2.2 seconds taken by the example plan).

Can you give more information?  I know that I'm not exactly certain what
the situation is from the above and the original query/explain piece.

In response to

Responses

pgsql-performance by date

Next:From: Josh BerkusDate: 2004-02-19 01:18:22
Subject: Re: Forcing filter/join order?
Previous:From: Peter DarleyDate: 2004-02-19 00:40:33
Subject: Re: Forcing filter/join order?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group