Re: pgsql: Allow using the updated tuple while moving it to a different par
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Amit Kapila <akapila@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Date: 2018-07-12T07:59:09Z
Lists: pgsql-hackers
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
Commits
-
Remove race-prone hot_standby_feedback test cases in 001_stream_rep.pl.
- ade18277a0dc 11.0 landed
- a360f952ff02 12.0 landed
- 5c513db12c29 10.5 landed
-
Allow using the updated tuple while moving it to a different partition.
- 40ca70ebcc9d 12.0 cited
-
Allow UPDATE to move rows between partitions.
- 2f178441044b 11.0 cited