Zdenek Kotala <[EMAIL PROTECTED]> writes:
> Does it mean that these function are every time called with heap tuple or
> untoasted row type (composite data type)? What is purpose of these function.
Legacy support for third-party modules. They're really pretty much
deprecated but I don't foresee
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
GetAttributeByNum has first parameter as HeapTupleHeader, but most functions
use Datum and after that they call DatumGetHeapTupleHeader. The difference is
that DatumGetHeapTupleHeader performs detoast on tuple(row type).
Is it in
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> GetAttributeByNum has first parameter as HeapTupleHeader, but most functions
> use Datum and after that they call DatumGetHeapTupleHeader. The difference is
> that DatumGetHeapTupleHeader performs detoast on tuple(row type).
> Is it intention do not d
GetAttributeByNum has first parameter as HeapTupleHeader, but most functions
use Datum and after that they call DatumGetHeapTupleHeader. The difference is
that DatumGetHeapTupleHeader performs detoast on tuple(row type).
Is it intention do not detoast in these functions or it is a bug?
