| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Introduce traversalValue for SP-GiST scan |
| Date: | 2016-03-30 15:37:56 |
| Message-ID: | E1alIBw-0001K1-GV@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Introduce traversalValue for SP-GiST scan
During scan sometimes it would be very helpful to know some information about
parent node or all ancestor nodes. Right now reconstructedValue could be used
but it's not a right usage of it (range opclass uses that).
traversalValue is arbitrary piece of memory in separate MemoryContext while
reconstructedVale should have the same type as indexed column.
Subsequent patches for range opclass and quad4d tree will use it.
Author: Alexander Lebedev, Teodor Sigaev
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/ccd6eb49a4ae924290ab7eba5540218f5beb48b8
Modified Files
--------------
doc/src/sgml/spgist.sgml | 15 +++++++++++++++
src/backend/access/spgist/spgscan.c | 18 ++++++++++++++++++
src/include/access/spgist.h | 4 ++++
3 files changed, 37 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2016-03-30 15:39:58 | pgsql: Use traversalValue in SP-GiST range opclass. |
| Previous Message | pgsql | 2016-03-30 14:24:43 | pgsql: Tag refs/tags/REL9_4_7 was created |