Re: recovery from xid wraparound

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Shane Wright" <shane(dot)wright(at)edigitalresearch(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, "Martijn van Oosterhout" <kleptog(at)svana(dot)org>
Subject: Re: recovery from xid wraparound
Date: 2006-10-24 15:24:01
Message-ID: 9293.1161703441@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Shane Wright" <shane(dot)wright(at)edigitalresearch(dot)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 or does 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 are more 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tony Caduto 2006-10-24 15:49:11 Re: performace review
Previous Message Martijn van Oosterhout 2006-10-24 15:21:55 Re: recovery from xid wraparound