Hi hackers,
> TupleTableSlot is a more abstract concept, being a container
> for a tuple that can be present in several different forms.
> It can contain a concrete tuple (HeapTupleData), or a "virtual"
> tuple that is just an array of Datum+isnull values. The executor
> usually uses tuple slots
Ajay P S writes:
> I am pretty new to the Postgres code base. I would like to know the
> difference between HeapTupleData and TupleTableSlot structures.
HeapTupleData is just a pointer to a concrete tuple. It exists
mainly because it's often convenient to pass around the tupl
Hi,
I am pretty new to the Postgres code base. I would like to know the
difference between HeapTupleData and TupleTableSlot structures.
Basically I am trying to understand some of the table access methods like
heap_insert, heap_getnext, heap_getnextslot etc where some accepts
Heaptuple as input
