From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Forcing filter/join order?
Date: Wed, 18 Feb 2004 16:30:43 -0800
Message-ID: <200402181630.43503.josh@agliodbs.com> (raw)
In-Reply-To: <200402181610.31978.josh@agliodbs.com>
References: <200402181610.31978.josh@agliodbs.com>
Folks,
Hmmm posted too soon. Figured out the problem:
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).
Is this the sort of thing which is ever likely to get fixed, or just a
fundamental limitation of index algorithms? Would using a non B-Tree index
allow me to work around this?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com
Subject: Re: Forcing filter/join order?
In-Reply-To: <200402181630.43503.josh@agliodbs.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