pgsql: Don't rely on uninitialized value in MERGE / DELETE - Mailing list pgsql-committers

From Alvaro Herrera
Subject pgsql: Don't rely on uninitialized value in MERGE / DELETE
Date
Msg-id E1pSNc1-001JRm-7d@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Don't rely on uninitialized value in MERGE / DELETE

On MERGE / WHEN MATCHED DELETE it's not possible to get cross-partition
updates, so we don't initialize cpUpdateRetrySlot; however, the code was
not careful to ignore the value in that case.  Make it do so.

Backpatch to 15.

Reported-by: Alexander Lakhin <exclusion@gmail.com>
Reviewed-by: Dean Rasheed <dean.a.rasheed@gmail.com>
Discussion: https://postgr.es/m/17792-0f89452029662c36@postgresql.org

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/5d8ec1b9f625be800c8db93408e7c0553356fcd3

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


pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Rename force_parallel_mode to debug_parallel_query
Next
From: Michael Paquier
Date:
Subject: pgsql: Add description for new patterns supported in HBA and ident samp