From: Michael Paquier <michael@paquier.xyz>
To: Amit Kapila <akapila@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Allow using the updated tuple while moving it to a different par
Date: Thu, 12 Jul 2018 16:59:09 +0900
Message-ID: <20180712075909.GG7352@paquier.xyz> (raw)
In-Reply-To: <E1fdW6s-00054K-QA@gemulon.postgresql.org>
References: <E1fdW6s-00054K-QA@gemulon.postgresql.org>
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%3A0...
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, akapila@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Allow using the updated tuple while moving it to a different par
In-Reply-To: <20180712075909.GG7352@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox