Re: Reorderbuffer crash during recovery - Mailing list pgsql-bugs

From vignesh C
Subject Re: Reorderbuffer crash during recovery
Date
Msg-id CALDaNm3XSXFed++sRSCu27XOQcEWsXcx1+2a3LGs1V+a3WXDpQ@mail.gmail.com
Whole thread Raw
In response to Re: Reorderbuffer crash during recovery  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Reorderbuffer crash during recovery
Re: Reorderbuffer crash during recovery
Re: Reorderbuffer crash during recovery
Re: Reorderbuffer crash during recovery
List pgsql-bugs
On Thu, Jan 16, 2020 at 9:17 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> One minor comment.  Otherwise, the patch looks fine to me.
> + /*
> + * We set final_lsn on a transaction when we decode its commit or abort
> + * record, but we never see those records for crashed transactions.  To
> + * ensure cleanup of these transactions, set final_lsn to that of their
> + * last change; this causes ReorderBufferRestoreCleanup to do the right
> + * thing. Final_lsn would have been set with commit_lsn earlier when we
> + * decode it commit, no need to update in that case
> + */
> + if (txn->final_lsn < change->lsn)
> + txn->final_lsn = change->lsn;
>
> /decode it commit,/decode its commit,
>

Thanks Dilip for reviewing.
I have fixed the comments you have suggested.

Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #16212: subquery block allows to overwrite table aliasdefined earlier
Next
From: Dilip Kumar
Date:
Subject: Re: Reorderbuffer crash during recovery