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

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

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] make async slave to wait for lsn to be replayed
Next
From: btnakamichin
Date:
Subject: Re: Feature improvement for pg_stat_statements