From: Markus Schaber <schabios@logi-track.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Performance List <pgsql-performance@postgresql.org>
Cc: PostGIS Users Discussion <postgis-users@postgis.refractions.net>
Subject: Re: Bad query optimizer misestimation because of TOAST
Date: Mon, 07 Feb 2005 15:07:44 +0100
Message-ID: <42077630.5020802@logi-track.com> (raw)
In-Reply-To: <9501.1107388153@sss.pgh.pa.us>
References: <42010C24.90301@logi-track.com>
<188.1107366272@sss.pgh.pa.us>
<42011B0B.2050305@logi-track.com>
<9501.1107388153@sss.pgh.pa.us>
Hi, Tom,
Tom Lane schrieb:
> Markus Schaber <schabios@logi-track.com> writes:
>> [Query optimizer misestimation using lossy GIST on TOASTed columns]
>
> What I would be inclined to do is to extend ANALYZE to make an estimate
> of the extent of toasting of every toastable column, and then modify
> cost_qual_eval to charge a nonzero cost for evaluation of Vars that are
> potentially toasted.
What to do now? To fix this issue seems to be a rather long-term job.
Is it enough to document workarounds (as in PostGIS), provided that
there are such workarounds for other GIST users?
Is there a bug tracking system we could file the problem, so it does not
get lost?
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, tgl@sss.pgh.pa.us, postgis-users@postgis.refractions.net
Subject: Re: Bad query optimizer misestimation because of TOAST
In-Reply-To: <42077630.5020802@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