pgsql: Evade extra table_tuple_fetch_row_version() in ExecUpdate()/Exec - Mailing list pgsql-committers

From Alexander Korotkov
Subject pgsql: Evade extra table_tuple_fetch_row_version() in ExecUpdate()/Exec
Date
Msg-id E1pf5zQ-004tAj-Sp@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/764da7710bf68eebb2c0facb2f871bc3c7a705b6

Modified Files
--------------
src/backend/executor/nodeModifyTable.c | 48 +++++++++++++++++++++++++---------
1 file changed, 35 insertions(+), 13 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix new test case to work on (some?) big-endian architectures.
Next
From: Thomas Munro
Date:
Subject: pgsql: Improve the naming of Parallel Hash Join phases.