On Thu, Jul 12, 2018 at 07:33:54AM +0000, Amit Kapila wrote:
> Allow using the updated tuple while moving it to a different partition.
>
> An update that causes the tuple to be moved to a different partition was
> missing out on re-constructing the to-be-updated tuple, based on the latest
> tuple in the update chain. Instead, it's simply deleting the latest tuple
> and inserting a new tuple in the new partition based on the old tuple.
> Commit 2f17844104 didn't consider this case, so some of the updates were
> getting lost.
>
> In passing, change the argument order for output parameter in ExecDelete
> and add some commentary about it.
Looks unrelated, but flaviventris (a snake?) has just complained:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2018-07-12%2007%3A36%3A01
--
Michael