Re: Strange issue with GiST index scan taking far too long - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Strange issue with GiST index scan taking far too long
Date
Msg-id 21579.1213032314@sss.pgh.pa.us
Whole thread Raw
In response to Re: Strange issue with GiST index scan taking far too long  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Strange issue with GiST index scan taking far too long  (Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> On Mon, 2008-06-09 at 11:49 -0400, Tom Lane wrote:
>> Is the value you are fetching from the geography table large enough to
>> be toasted?  I'm thinking you might be looking at the cost of repeated
>> de-toastings.

> So you are saying it is de-toasted 32880 times, in this case? If not,
> where are the repeated de-toastings happening?

Inside the index support functions.  I'm thinking we could fix this by
forcibly detoasting values passed as index scan keys, but it's not quite
clear where's the best place to do that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: proposal: new contrib module - session variables
Next
From: Tom Lane
Date:
Subject: Re: Proposal: GiST constraints