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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: cca5507 <cca5507(at)qq(dot)com>
Cc: Ajin Cherian <itsajin(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, 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-07-01 23:47:03
Message-ID: aGRzdwwD0Ei-xi5k@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 28, 2025 at 11:44:52AM +0800, cca5507 wrote:
> If I understand correctly, this may break the basic&nbsp;principle:
>
> The aim is to build a&nbsp;snapshot that behaves the same as a
> freshly taken MVCC snapshot would have&nbsp;at the time the
> XLogRecord was generated.

Please note that we prefer bottom-posting when sending messages on
pgsql-hackers and the community mailing lists, as defined in this
link:
https://en.wikipedia.org/wiki/Posting_style#Bottom-posting

Top-posting, as you did in your last email, is breaking the logic and
flow of the discussion.

Some more useful documentation from the PostgreSQL wiki:
https://wiki.postgresql.org/wiki/Mailing_Lists
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-07-01 23:53:06 Re: GNU/Hurd portability patches
Previous Message Michael Paquier 2025-07-01 23:42:41 Re: Improve explicit cursor handling in pg_stat_statements