Re: Assertion failure with replication origins and PREPARE TRANSACTIOn

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Assertion failure with replication origins and PREPARE TRANSACTIOn
Date: 2021-12-14 02:14:25
Message-ID: Ybf+ASU/+Wgdv65A@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 13, 2021 at 07:53:43PM +0900, Michael Paquier wrote:
> Well, I don't think that it is a big deal one way or the other, as
> we'd finish with InvalidXLogRecPtr for the LSN and 0 for the timestamp
> anyway. If both of you feel that just removing the assertion rather
> than adding an extra check is better, that's fine by me :)

Looked at that today, and done this way. The tests have been extended
a bit more with one ROLLBACK and one ROLLBACK PREPARED, while checking
for the contents decoded.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message houzj.fnst@fujitsu.com 2021-12-14 02:23:14 RE: parallel vacuum comments
Previous Message tanghy.fnst@fujitsu.com 2021-12-14 02:10:33 RE: parallel vacuum comments