Re: GetOldestXmin going backwards is dangerous after all

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: GetOldestXmin going backwards is dangerous after all
Дата
Msg-id CA+U5nMJDWuTS3G5cZMmQGutqOZO+xAuZvgSV9QyWgtjj24vydQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: GetOldestXmin going backwards is dangerous after all  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: GetOldestXmin going backwards is dangerous after all  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения 
On 4 February 2013 17:02, Andres Freund <andres@2ndquadrant.com> wrote:

> I unfortunately don't yet see a robust way without storing the last used
> horizon :(.

We can't go backwards, but we can go forwards.

We can move the next xid forwards by an amount equal to the increase
in vacuum_defer_cleanup_age.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: GetOldestXmin going backwards is dangerous after all
Следующее
От: Andres Freund
Дата:
Сообщение: Re: GetOldestXmin going backwards is dangerous after all