Re: problem with RETURNING and update row movement - Mailing list pgsql-hackers

From Amit Langote
Subject Re: problem with RETURNING and update row movement
Date
Msg-id CA+HiwqEH9k4soXg3LxJFof2Biou2p77g6ja5iSTQCH9DBy5b5g@mail.gmail.com
Whole thread Raw
In response to Re: problem with RETURNING and update row movement  (Michael Paquier <michael@paquier.xyz>)
Responses Re: problem with RETURNING and update row movement  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
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.

-- 
Amit Langote
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: legrand legrand
Date:
Subject: Re: [PATCH] Add features to pg_stat_statements
Next
From: Daniel Wood
Date:
Subject: Re: The ultimate extension hook.