diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2015-03-26 23:07:52 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2015-03-26 23:07:52 +0200 |
| commit | 55b59eda13a742f8af913734e22ecc8a21754414 (patch) | |
| tree | 4bbe77575d9eb2f27d0c770d07fc10095ea329f6 /src/backend/access/gist/gistutil.c | |
| parent | 785941cdc359c6e595201ffb0df9d28f3f7173a4 (diff) | |
| download | postgresql-55b59eda13a742f8af913734e22ecc8a21754414.tar.gz | |
Fix GiST index-only scans for opclasses with different storage type.
We cannot use the index's tuple descriptor directly to describe the index
tuples returned in an index-only scan. That's because the index might use
a different datatype for the values stored on disk than the type originally
indexed. As long as they were both pass-by-ref, it worked, but will not work
for pass-by-value types of different sizes. I noticed this as a crash when I
started hacking a patch to add fetch methods to btree_gist.
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
| -rw-r--r-- | src/backend/access/gist/gistutil.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/gist/gistutil.c b/src/backend/access/gist/gistutil.c index 1680251a18..bf9fbf30a8 100644 --- a/src/backend/access/gist/gistutil.c +++ b/src/backend/access/gist/gistutil.c @@ -657,7 +657,7 @@ gistFetchTuple(GISTSTATE *giststate, Relation r, IndexTuple tuple) } MemoryContextSwitchTo(oldcxt); - return index_form_tuple(giststate->tupdesc, fetchatt, isnull); + return index_form_tuple(giststate->fetchTupdesc, fetchatt, isnull); } float |