From: Adrian Klaver <adrian.klaver@aklaver.com>
To: jacktby@gmail.com <jacktby@gmail.com>
To: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: what's hsitoric MVCC Snapshot?
Date: Sun, 5 Mar 2023 08:00:38 -0800
Message-ID: <f217a125-798f-ac2e-df83-349093cd47ff@aklaver.com> (raw)
In-Reply-To: <3bff79c9-5118-1e73-69d7-04a9b7c83c0e@aklaver.com>
References: <202303052249108283258@gmail.com>
<3bff79c9-5118-1e73-69d7-04a9b7c83c0e@aklaver.com>
On 3/5/23 07:58, Adrian Klaver wrote:
> On 3/5/23 06:49, jacktby@gmail.com wrote:
>> Here are the comments in src/include/utils/snapshot.h.
>> /*
>> * For normal MVCC snapshot this contains the all xact IDs that are in
>> * progress, unless the snapshot was taken during recovery in which case
>> * it's empty. For historic MVCC snapshots, the meaning is inverted, i.e.
>> * it contains *committed* transactions between xmin and xmax.
>> *
>> * note: all ids in xip[] satisfy xmin <= xip[i] < xmax
>> */
>> TransactionId *xip;
>> I can't understand the historic MVCC snapshots? can you give me
>> a scenario
>> to describe this?
>
> From the same file:
>
>
> /*
> * A tuple is visible iff it follows the rules of SNAPSHOT_MVCC, but
> * supports being called in timetravel context (for decoding catalog
> * contents in the context of logical decoding).
> */
> SNAPSHOT_HISTORIC_MVCC,
Also:
typedef struct SnapshotData *Snapshot;
#define InvalidSnapshot ((Snapshot) NULL)
/*
* Struct representing all kind of possible snapshots.
*
* There are several different kinds of snapshots:
* * Normal MVCC snapshots
* * MVCC snapshots taken during recovery (in Hot-Standby mode)
* * Historic MVCC snapshots used during logical decoding
* * snapshots passed to HeapTupleSatisfiesDirty()
* * snapshots passed to HeapTupleSatisfiesNonVacuumable()
* * snapshots used for SatisfiesAny, Toast, Self where no members are
* accessed.
*
* TODO: It's probably a good idea to split this struct using a NodeTag
* similar to how parser and executor nodes are handled, with one type for
* each different kind of snapshot to avoid overloading the meaning of
* individual fields.
*/
>
>> ------------------------------------------------------------------------
>> jacktby@gmail.com
>
--
Adrian Klaver
adrian.klaver@aklaver.com
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, jacktby@gmail.com
Subject: Re: what's hsitoric MVCC Snapshot?
In-Reply-To: <f217a125-798f-ac2e-df83-349093cd47ff@aklaver.com>
References: <202303052249108283258@gmail.com> <3bff79c9-5118-1e73-69d7-04a9b7c83c0e@aklaver.com> <f217a125-798f-ac2e-df83-349093cd47ff@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox