From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Forcing filter/join order?
Date: Wed, 18 Feb 2004 16:56:22 -0800 (PST)
Message-ID: <20040218165410.G36125@megazone.bigpanda.com> (raw)
In-Reply-To: <200402181630.43503.josh@agliodbs.com>
References: <200402181610.31978.josh@agliodbs.com>
<200402181630.43503.josh@agliodbs.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sszabo@megazone.bigpanda.com, josh@agliodbs.com
Subject: Re: Forcing filter/join order?
In-Reply-To: <20040218165410.G36125@megazone.bigpanda.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox