@@ -164,7 +164,7 @@ typedef struct TableAmRoutine
164
164
* synchronized scans, or page mode may be used (although not every AM
165
165
* will support those).
166
166
*
167
- * is_{bitmapscan, samplescan} specify whether the scan is inteded to
167
+ * is_{bitmapscan, samplescan} specify whether the scan is intended to
168
168
* support those types of scans.
169
169
*
170
170
* if temp_snap is true, the snapshot will need to be deallocated at
@@ -220,7 +220,7 @@ typedef struct TableAmRoutine
220
220
Size (* parallelscan_initialize ) (Relation rel , ParallelTableScanDesc pscan );
221
221
222
222
/*
223
- * Reinitilize `pscan` for a new scan. `rel` will be the same relation as
223
+ * Reinitialize `pscan` for a new scan. `rel` will be the same relation as
224
224
* when `pscan` was initialized by parallelscan_initialize.
225
225
*/
226
226
void (* parallelscan_reinitialize ) (Relation rel , ParallelTableScanDesc pscan );
@@ -913,7 +913,7 @@ table_delete(Relation rel, ItemPointer tid, CommandId cid,
913
913
* Input parameters:
914
914
* relation - table to be modified (caller must hold suitable lock)
915
915
* otid - TID of old tuple to be replaced
916
- * newtup - newly constructed tuple data to store
916
+ * slot - newly constructed tuple data to store
917
917
* cid - update command ID (used for visibility test, and stored into
918
918
* cmax/cmin if successful)
919
919
* crosscheck - if not InvalidSnapshot, also check old tuple against this
@@ -929,8 +929,8 @@ table_delete(Relation rel, ItemPointer tid, CommandId cid,
929
929
* TM_SelfModified, TM_Updated, or TM_BeingModified
930
930
* (the last only possible if wait == false).
931
931
*
932
- * On success, the header fields of *newtup are updated to match the new
933
- * stored tuple; in particular, newtup->t_self is set to the TID where the
932
+ * On success, the slot's tts_tid and tts_tableOid are updated to match the new
933
+ * stored tuple; in particular, slot->tts_tid is set to the TID where the
934
934
* new tuple was inserted, and its HEAP_ONLY_TUPLE flag is set iff a HOT
935
935
* update was done. However, any TOAST changes in the new tuple's
936
936
* data are not reflected into *newtup.
@@ -965,7 +965,7 @@ table_update(Relation rel, ItemPointer otid, TupleTableSlot *slot,
965
965
* flags:
966
966
* If TUPLE_LOCK_FLAG_LOCK_UPDATE_IN_PROGRESS, follow the update chain to
967
967
* also lock descendant tuples if lock modes don't conflict.
968
- * If TUPLE_LOCK_FLAG_FIND_LAST_VERSION, update chain and lock lastest
968
+ * If TUPLE_LOCK_FLAG_FIND_LAST_VERSION, update chain and lock latest
969
969
* version.
970
970
*
971
971
* Output parameters:
0 commit comments