Robert Haas <> writes:
> Hmm, I guess there is a bit of a hotspot in StoreIndexTuple, which is
> probably being folded into IndexOnlyNext in the per-function timings:

>     ExecClearTuple(slot);
>     for (i = 0; i < nindexatts; i++)
>         values[i] = index_getattr(itup, i + 1, itupdesc, &isnull[i]);
>     ExecStoreVirtualTuple(slot);

I had wondered whether it'd be worth optimizing that along the lines of
slot_getallattrs().  But most indexes probably have only one column,
or anyway not enough to make for a useful savings.

                        regards, tom lane

Sent via pgsql-hackers mailing list (
To make changes to your subscription:

Reply via email to