From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "jacktby(at)gmail(dot)com" <jacktby(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: what's hsitoric MVCC Snapshot? |
Date: | 2023-03-05 15:58:47 |
Message-ID: | 3bff79c9-5118-1e73-69d7-04a9b7c83c0e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/5/23 06:49, jacktby(at)gmail(dot)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,
> ------------------------------------------------------------------------
> jacktby(at)gmail(dot)com
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-03-05 16:00:38 | Re: what's hsitoric MVCC Snapshot? |
Previous Message | jacktby@gmail.com | 2023-03-05 14:49:13 | what's hsitoric MVCC Snapshot? |