Re: Index-only scans for multicolumn GIST

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Index-only scans for multicolumn GIST
Date: 2014-07-22 14:06:01
Message-ID: 21665.1406037961@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> For a circle, the GiST index stores a bounding box of the circle. The
> new fetch function reverses that, calculating the radius and center of
> the circle from the bounding box.

> Those conversions lose some precision due to rounding. Are we okay with
> that?

That seems like a nonstarter :-(. Index-only scans don't have a license
to return approximations. If we drop the behavior for circles, how much
functionality do we have left?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-07-22 14:06:03 Re: Index-only scans for multicolumn GIST
Previous Message Robert Haas 2014-07-22 13:39:13 Re: [bug fix] Suppress "autovacuum: found orphan temp table" message