| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Etsuro Fujita <etsuro(dot)fujita(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 05:26:04 |
| Message-ID: | CA+HiwqEH9k4soXg3LxJFof2Biou2p77g6ja5iSTQCH9DBy5b5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 24, 2020 at 1:54 PM Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Wood | 2020-09-24 05:40:52 | Re: The ultimate extension hook. |
| Previous Message | legrand legrand | 2020-09-24 05:15:23 | Re: [PATCH] Add features to pg_stat_statements |