| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Move ModifyTableContext->lockmode to UpdateContext |
| Date: | 2022-04-20 09:26:57 |
| Message-ID: | E1nh6bx-000FEs-9C@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)paquier(dot)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(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-04-20 11:44:36 | pgsql: set_deparse_plan: Reuse variable to appease Coverity |
| Previous Message | Alvaro Herrera | 2022-04-20 08:35:44 | pgsql: ExecModifyTable: use context.planSlot instead of planSlot |