Re: advancing snapshot's xmin - Mailing list pgsql-hackers

From Tom Lane
Subject Re: advancing snapshot's xmin
Date
Msg-id 3803.1206716399@sss.pgh.pa.us
Whole thread Raw
In response to Re: advancing snapshot's xmin  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: advancing snapshot's xmin
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> As far as I can see, for the purposes of VACUUM we can remove any tuple
> that was deleted after the old transaction's Xid but before that
> transaction's Xmin (i.e. all of its live snapshots).  This means we get
> to ignore Xid in GetOldestXmin and in the TransactionXmin calculations
> in GetSnapshotData.  It would not surprise me, however, to find out that
> I am overlooking something and this is incorrect.

This seems entirely off-base to me.  In particular, if a transaction
has an XID then its XMIN will never be greater than that, so I don't
even see how you figure the case will arise.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Suresh
Date:
Subject: segfault in locking code
Next
From: Alvaro Herrera
Date:
Subject: Re: advancing snapshot's xmin