Re: SP-GiST for ranges based on 2d-mapping and quad-tree
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Alexander Korotkov <aekorotkov@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-08-20T15:32:33Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Teach SP-GiST to do index-only scans.
- 922036249340 9.2.0 cited
Jeff Davis <pgsql@j-davis.com> writes: > On Sat, 2012-07-28 at 17:50 -0400, Tom Lane wrote: >> which would come >> back to bite us if we ever try to support index-only scans with SPGiST. > I'm confused: > http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=92203624934095163f8b57b5b3d7bbd2645da2c8 Sorry, I was being imprecise there. What I meant was that an opclass that abused the reconstructed-value storage for something else might have problems supporting index-only scans. If we think opclasses might need private storage for index searches, we should add that as a new part of the API, not tell them to misuse this part. regards, tom lane