On 2022-Mar-20, Tom Lane wrote:
> ==2663594== Conditional jump or move depends on uninitialised value(s)
> ==2663594==at 0x421526: ExecUpdateAct (nodeModifyTable.c:1855)
> It reproduces easily for me under valgrind. I guess
> ExecCrossPartitionUpdate must be failing to set
> inserted_tuple o
Alvaro Herrera writes:
> Enforce foreign key correctly during cross-partition updates
skink is not too happy with this:
==2663594== VALGRINDERROR-BEGIN
==2663594== Conditional jump or move depends on uninitialised value(s)
==2663594==at 0x421526: ExecUpdateAct (nodeModifyTable.c:1855)
==2663
Enforce foreign key correctly during cross-partition updates
When an update on a partitioned table referenced in foreign key
constraints causes a row to move from one partition to another,
the fact that the move is implemented as a delete followed by an insert
on the target partition causes the fo
