public inbox for [email protected]  

help / color / mirror / Atom feed

From: =?ISO-8859-1?B?Y2NhNTUwNw==?= <[email protected]>
To: =?ISO-8859-1?B?QWppbiBDaGVyaWFu?= <[email protected]>
Cc: =?ISO-8859-1?B?QmVydHJhbmQgRHJvdXZvdA==?= <[email protected]>
Cc: =?ISO-8859-1?B?TWljaGFlbCBQYXF1aWVy?= <[email protected]>
Cc: =?ISO-8859-1?B?cGdzcWwtaGFja2Vycw==?= <[email protected]>
Subject: Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state
Date: Thu, 27 Mar 2025 11:47:32 +0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFPTHDa0B0a7yL90r1Rh4dAd+Q-mozYnGO26eXf7wxmpMF7NEQ@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<CAFPTHDa0B0a7yL90r1Rh4dAd+Q-mozYnGO26eXf7wxmpMF7NEQ@mail.gmail.com>

Hi,

According to the comment above DecodeTXNNeedSkip(), transactions committed before SNAPBUILD_CONSISTENT state won't be decoded. It's important for initial table data synchronization because the table sync workers use the consistent snapshot to copy data so transactions before SNAPBUILD_CONSISTENT are already included in the initial data.


This change may be redundant with SnapBuildXactNeedsSkip(), I add just for safe.


--
Regards,
ChangAo Chen

view thread (19+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox