• T
    Revise TupleTableSlot code to avoid unnecessary construction and disassembly · f97aebd1
    Tom Lane 提交于
    of tuples when passing data up through multiple plan nodes.  A slot can now
    hold either a normal "physical" HeapTuple, or a "virtual" tuple consisting
    of Datum/isnull arrays.  Upper plan levels can usually just copy the Datum
    arrays, avoiding heap_formtuple() and possible subsequent nocachegetattr()
    calls to extract the data again.  This work extends Atsushi Ogawa's earlier
    patch, which provided the key idea of adding Datum arrays to TupleTableSlots.
    (I believe however that something like this was foreseen way back in Berkeley
    days --- see the old comment on ExecProject.)  A test case involving many
    levels of join of fairly wide tables (about 80 columns altogether) showed
    about 3x overall speedup, though simple queries will probably not be
    helped very much.
    
    I have also duplicated some code in heaptuple.c in order to provide versions
    of heap_formtuple and friends that use "bool" arrays to indicate null
    attributes, instead of the old convention of "char" arrays containing either
    'n' or ' '.  This provides a better match to the convention used by
    ExecEvalExpr.  While I have not made a concerted effort to get rid of uses
    of the old routines, I think they should be deprecated and eventually removed.
    f97aebd1
tstoreReceiver.c 1.9 KB