From: Markus Schaber <schabios@logi-track.com>
To: PostgreSQL Performance List <pgsql-performance@postgresql.org>
To: PostGIS Users Discussion <postgis-users@postgis.refractions.net>
Subject: Re: [postgis-users] Bad query optimizer misestimation because of
Date: Thu, 03 Feb 2005 14:59:25 +0100
Message-ID: <42022E3D.80108@logi-track.com> (raw)
In-Reply-To: <42010C24.90301@logi-track.com>
References: <42010C24.90301@logi-track.com>
Hi, all,
Markus Schaber schrieb:
> As a small workaround, I could imagine to add a small additional column
> in the table that contains the geometry's bbox, and which I use the &&
> operator against. This should avoid touching the TOAST for the skipped rows.
For your personal amusement: I just noticed that, after adding the
additional column containing the bbox and running VACUUM FULL, the table
now has a size of 4 pages, and that's enough for the query optimizer to
choose an index scan. At least that saves us from modifying and
redeploying a bunch of applications to use the && bbox query:-)
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com
Attachments:
signature.asc (application/pgp-signature, 255B) download
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: schabios@logi-track.com, postgis-users@postgis.refractions.net
Subject: Re: [postgis-users] Bad query optimizer misestimation because of
In-Reply-To: <42022E3D.80108@logi-track.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