chris smith wrote:
1.6secs isn't too bad on 4.3mill rows...
How many entries are there for that date range?
1.7 secs /is/ good - it typically takes 5 or 6 seconds, which isn't so
good. My question is 'why does the planner choose such a bizarre range
request when both elements of the 'between' are identical? :)'
If I replace the
(allocation0_."Date" between '2006-06-09 00:00:00.000000' and
'2006-06-09 00:00:00.000000')
with
allocation0_."Date" ='2006-04-09 00:00:00.000000'
then the query comes back in a few milliseconds (as I'd expect :) - and
yup I've been using different dates for each test to avoid the query
being cached.
For ref, there are typically 35000 rows per date :)
Cheers,
Gavin.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
