Evade extra table_tuple_fetch_row_version() in ExecUpdate()/ExecDelete()

Alexander Korotkov <akorotkov@postgresql.org>

Commit: 764da7710bf68eebb2c0facb2f871bc3c7a705b6
Author: Alexander Korotkov <akorotkov@postgresql.org>
Date: 2023-03-22T21:26:59Z
Releases: 16.0
Evade extra table_tuple_fetch_row_version() in ExecUpdate()/ExecDelete()

When we lock tuple using table_tuple_lock() then we at the same time fetch
the locked tuple to the slot.  In this case we can skip extra
table_tuple_fetch_row_version() thank to we've already fetched the 'old' tuple
and nobody can change it concurrently since it's locked.

Discussion: https://postgr.es/m/CAPpHfdua-YFw3XTprfutzGp28xXLigFtzNbuFY8yPhqeq6X5kg%40mail.gmail.com
Reviewed-by: Aleksander Alekseev, Pavel Borisov, Vignesh C, Mason Sharp
Reviewed-by: Andres Freund, Chris Travers

Files

PathChange+/−
src/backend/executor/nodeModifyTable.c modified +35 −13

Discussion