* Update a tuple. * * NB: do not call this directly unless you are prepared to deal with * concurrent-update conditions. Use simple_table_tuple_update instead. * * Input parameters: * relation - table to be modified (caller must hold suitable lock) * otid - TID of old tuple to be replaced * slot - newly constructed tuple data to store * cid - update command ID (used for visibility test,
| 1733 | * for additional info. |
| 1734 | */ |
| 1735 | static inline TM_Result |
| 1736 | table_tuple_update(Relation rel, ItemPointer otid, TupleTableSlot *slot, |
| 1737 | CommandId cid, Snapshot snapshot, Snapshot crosscheck, |
| 1738 | bool wait, TM_FailureData *tmfd, LockTupleMode *lockmode, |
| 1739 | bool *update_indexes) |
| 1740 | { |
| 1741 | return rel->rd_tableam->tuple_update(rel, otid, slot, |
| 1742 | cid, snapshot, crosscheck, |
| 1743 | wait, tmfd, |
| 1744 | lockmode, update_indexes); |
| 1745 | } |
| 1746 | |
| 1747 | /* |
| 1748 | * Lock a tuple in the specified mode. |
no outgoing calls
no test coverage detected