Re: recovery from xid wraparound - Mailing list pgsql-general

From Tom Lane
Subject Re: recovery from xid wraparound
Date
Msg-id 9293.1161703441@sss.pgh.pa.us
Whole thread Raw
In response to Re: recovery from xid wraparound  ("Shane Wright" <shane.wright@edigitalresearch.com>)
List pgsql-general
"Shane Wright" <shane.wright@edigitalresearch.com> writes:
> If I change vacuum_mem I'll need to at least 'pg_ctl reload' - will it apply straightaway with the next vacuum query
ordoes it need a full restart? 

reload is enough.

> Basically if its just datfrozenxid that's not updated I can live with delaying the vacuum a few days.  But if things
aremore serious then obviously I can't wait. 

The question is how close to the wraparound horizon is any of your data.
We don't really know that --- the datfrozenxid provides a lower bound
but we don't know where things are in reality.  Also, are you prepared
to tolerate wrong answers (missing rows) for awhile?  As Martijn
mentioned, the vacuum will retrieve rows that have slid past the wrap
horizon, but they'll have been invisible to your queries meanwhile.

            regards, tom lane

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: recovery from xid wraparound
Next
From: Tony Caduto
Date:
Subject: Re: performace review