Re: problem with RETURNING and update row movement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, 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: 2021-04-22 15:49:10
Message-ID: 1094443.1619106550@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> I think we should also add slot != srcSlot to this condition.

Good idea, should save useless comparisons of identical tupdescs.
Done.

>> (I've not looked at porting this to v12 or v11 yet.)

> I did that; patches attached. (I haven't changed them to incorporate
> the above comment though.)

Thanks for that, saved me some work. I've pushed these.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-04-22 16:15:27 Re: decoupling table and index vacuum
Previous Message Mark Dilger 2021-04-22 15:46:09 Re: multi-install PostgresNode fails with older postgres versions