From: Rod Taylor <pg@rbt.ca>
To: ken <southerland@samsixedd.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Index oddity
Date: Wed, 09 Jun 2004 17:29:03 -0400
Message-ID: <1086816543.2539.98.camel@jester> (raw)
In-Reply-To: <1086814928.32077.259.camel@pesky>
References: <1086809460.32077.246.camel@pesky>
<1086811930.2539.90.camel@jester>
<1086814209.32077.252.camel@pesky>
<1086814597.2539.92.camel@jester>
<1086814928.32077.259.camel@pesky>
> ... and here is the plan with statistics set to 1000 ...
>
> Seq Scan on nrgfeature f (cost=0.00..31675.57 rows=18608 width=218)
> (actual time=63.544..1002.701 rows=225 loops=1)
> Filter: ((upperrightx > 321264.236977215::double precision) AND
> (lowerleftx < 324046.799812083::double precision) AND (upperrighty >
> 123286.261898636::double precision) AND (lowerlefty <
> 124985.927450476::double precision) AND (diagonalsize > 49.999::double
> precision))
It's better like this, but still way off the mark. Even your good query
which uses the index was out by more than an order of magnitude.
Try raising the statistics levels for upperrightx, lowerleftx,
upperrighty and lowerlefty.
Failing that, you might be able to push it back down again by giving
diagonalsize an upper limit. Perhaps 500 is a value that would never
occur.
AND (diagonalsize BETWEEN 49.999::double precision AND 500)
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: pg@rbt.ca, southerland@samsixedd.com
Subject: Re: Index oddity
In-Reply-To: <1086816543.2539.98.camel@jester>
* 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