Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state

From: cca5507 <cca5507(at)qq(dot)com>
To: Ajin Cherian <itsajin(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Historic snapshot doesn't track txns committed in BUILDING_SNAPSHOT state
Date: 2025-03-27 03:47:32
Message-ID: tencent_B54A1979BC9D8332BBADD092C2B8DA829407@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2025-03-27 04:26:53 RE: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.
Previous Message David G. Johnston 2025-03-27 03:44:37 Re: support ALTER TABLE DROP EXPRESSION for virtual generated column