pgsql: Move ModifyTableContext->lockmode to UpdateContext - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Move ModifyTableContext->lockmode to UpdateContext
Date
Msg-id E1nh6bx-000FEs-9C@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Move ModifyTableContext->lockmode to UpdateContext

Should have been done this way to start with, but I failed to notice
This way we avoid some pointless initialization, and better contains the
variable to exist in the scope where it is really used.

Reviewed-by: Michaël Paquier <michael@paquier.xyz>
Discussion: https://postgr.es/m/202204191345.qerjy3kxi3eb@alvherre.pgsql

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a87e75956926f966d90bdd1a6bd495cf59cdc3ad

Modified Files
--------------
src/backend/executor/nodeModifyTable.c | 23 ++++++++---------------
1 file changed, 8 insertions(+), 15 deletions(-)


pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: pgsql: ExecModifyTable: use context.planSlot instead of planSlot
Next
From: Alvaro Herrera
Date:
Subject: pgsql: set_deparse_plan: Reuse variable to appease Coverity