Re: problem with RETURNING and update row movement

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: problem with RETURNING and update row movement
Date: 2020-09-24 04:54:03
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message btnakamichin 2020-09-24 04:54:27 Re: Feature improvement for pg_stat_statements
Previous Message Michael Paquier 2020-09-24 04:51:39 Re: [HACKERS] make async slave to wait for lsn to be replayed