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

From Tom Lane
Subject Re: problem with RETURNING and update row movement
Date
Msg-id 1094443.1619106550@sss.pgh.pa.us
Whole thread Raw
In response to Re: problem with RETURNING and update row movement  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: problem with RETURNING and update row movement  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-hackers
Amit Langote <amitlangote09@gmail.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



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: multi-install PostgresNode fails with older postgres versions
Next
From: Robert Haas
Date:
Subject: Re: decoupling table and index vacuum