Hi hackers. I found a strange point when I was reading the heapam handlers of table access method, where heapam_tuple_insert and several handlers explicitly assign t_tableOid of the tuple to be operated, while later the t_tableOid is assigned again by like heap_prepare_insert or so. Is it redundant? Better to do it together with other tuple initialization code?
Regards, Jingtang
0001-Remove-redundant-assignment-of-HeapTuple-table-oid.patch
Description: Binary data
