Teodor Sigaev <[EMAIL PROTECTED]> writes:
> One reason why existing interface is not good:
> Who say, that for one heap tuple should exists only one index tuple?
Good point. Is that reason enough to change it? Not sure. The index
AM doesn't really have to bother with telling the truth in the
In
I can't offhand see a good reason to return the index tuple's tid.
One reason why existing interface is not good:
Who say, that for one heap tuple should exists only one index tuple?
For example, Oleg and Vadim Mikheev had discussian pair years ago about
indexing arrays by B-tree: for each heap t
Teodor Sigaev <[EMAIL PROTECTED]> writes:
> [ why do we have InsertIndexResult and not just a bool? ]
Good question. Perhaps it was used once upon a time? That API has been
like that since Berkeley days.
I can't offhand see a good reason to return the index tuple's tid.
There isn't any legitima
Hi!
Insert function of any type of index must returns palloced InsertIndexResult
(contains blkno and offset).
This result is returned by index_insert (backend/access/indexam/indexam.c).
This function is called in 3 places:
./access/heap/tuptoaster.c
./catalog/indexing.c
./executor/execUtils.c
Bu
