Re: what to revert

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: what to revert
Дата
Msg-id 20160505031435.jwlw3gq57acnjxkx@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: what to revert  (Ants Aasma <ants.aasma@eesti.ee>)
Ответы Re: what to revert  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On 2016-05-05 06:08:39 +0300, Ants Aasma wrote:
> On 5 May 2016 1:28 a.m., "Andres Freund" <andres@anarazel.de> wrote:
> > On 2016-05-04 18:22:27 -0400, Robert Haas wrote:
> > > How would the semantics change?
> >
> > Right now the time for computing the snapshot is relevant, if
> > maintenance of xids is moved, it'll likely be tied to the time xids are
> > assigned. That seems perfectly alright, but it'll change behaviour.
> 
> FWIW moving the maintenance to a clock tick process will not change user
> visible semantics in any significant way. The change could easily be made
> in the next release.

I'm not convinced of that - right now the timeout is computed as a
offset to the time a snapshot with a certain xmin horizon is
taken. Moving the computation to GetNewTransactionId() or a clock tick
process will make it relative to the time an xid has been generated
(minus a fuzz factor).  That'll behave differently in a number of cases, no?



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Ants Aasma
Дата:
Сообщение: Re: what to revert
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_dump vs. TRANSFORMs