Re: advancing snapshot's xmin

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: advancing snapshot's xmin
Дата
Msg-id 3803.1206716399@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: advancing snapshot's xmin  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: advancing snapshot's xmin  (Alvaro Herrera <alvherre@commandprompt.com>)
Список 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 по дате отправления:

Предыдущее
От: Suresh
Дата:
Сообщение: segfault in locking code
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: advancing snapshot's xmin