Re: Undo logs - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Undo logs
Date
Msg-id CAFiTN-tqpHbip3621ABQ_TNW6K7JO1-N8qvpiOaBE+JS2fnAvA@mail.gmail.com
Whole thread Raw
In response to Re: Undo logs  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Undo logs  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Wed, Jan 9, 2019 at 11:40 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
On Tue, Jan 8, 2019 at 2:11 PM Amit Kapila <amit.kapila16@gmail.com> wrote:


3.
+ work_txn.urec_next = uur->uur_next;
+ work_txn.urec_xidepoch = uur->uur_xidepoch;
+ work_txn.urec_progress = uur->uur_progress;
+ work_txn.urec_prevurp = uur->uur_prevurp;
+ work_txn.urec_dbid = uur->uur_dbid;

It would be better if we initialize these members in the order in
which they appear in the actual structure.  All other undo header
structures are initialized that way, so this looks out-of-place.
 
One more change in ReadUndoByte on same line. 

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: New vacuum option to do only freezing
Next
From: Etsuro Fujita
Date:
Subject: Re: Query with high planning time at version 11.1 compared versions10.5 and 11.0