Re: GetOldestXmin going backwards is dangerous after all - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: GetOldestXmin going backwards is dangerous after all
Date
Msg-id CA+U5nMJDWuTS3G5cZMmQGutqOZO+xAuZvgSV9QyWgtjj24vydQ@mail.gmail.com
Whole thread Raw
In response to Re: GetOldestXmin going backwards is dangerous after all  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: GetOldestXmin going backwards is dangerous after all
List 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 by date:

Previous
From: Andres Freund
Date:
Subject: Re: GetOldestXmin going backwards is dangerous after all
Next
From: Andres Freund
Date:
Subject: Re: GetOldestXmin going backwards is dangerous after all