Re: problem with RETURNING and update row movement
Amit Langote <amitlangote09@gmail.com>
From: Amit Langote <amitlangote09@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Etsuro Fujita <etsuro.fujita@gmail.com>,
Alvaro Herrera <alvherre@2ndquadrant.com>, Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-09-30T03:34:17Z
Lists: pgsql-hackers
On Thu, Sep 24, 2020 at 2:26 PM Amit Langote <amitlangote09@gmail.com> wrote: > On Thu, Sep 24, 2020 at 1:54 PM Michael Paquier <michael@paquier.xyz> wrote: > > On Thu, Sep 24, 2020 at 04:25:24AM +0900, Etsuro Fujita wrote: > > > Sorry, my thought was vague. To store xmin/xmax/cmin/cmax into a > > > given slot, we need to extend the TupleTableSlot struct to contain > > > these attributes as well? Or we need to introduce a new callback > > > routine for that (say, setsysattr)? These would not be > > > back-patchable, though. > > > > Please note that the latest patch fails to apply, so this needs a > > rebase. > > I saw the CF-bot failure too yesterday, although it seems that it's > because the bot is trying to apply the patch version meant for v11 > branch onto HEAD branch. I just checked that the patches apply > cleanly to their respective branches. I checked that the last statement is still true, so I've switched the status back to Needs Review. -- Amit Langote EnterpriseDB: http://www.enterprisedb.com
Commits
-
Fix bugs in RETURNING in cross-partition UPDATE cases.
- a71cfc56bf60 13.3 landed
- 3fb93103a9fd 12.7 landed
- 27835b547664 11.12 landed
-
postgres_fdw: Clean up handling of system columns.
- da7d44b627ba 9.6.0 cited