Re: Transaction id wraparound questions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marc Munro <marc(at)bloodnok(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Transaction id wraparound questions
Date: 2005-07-06 19:04:44
Message-ID: 29442.1120676684@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Marc Munro <marc(at)bloodnok(dot)com> writes:
> A recent vacuum of the entire database gave us the dreaded
> "You may have already suffered transaction-wraparound data loss."
> warning.

If you have in fact been vacuuming *every* table including all the
system catalogs, then you don't need to panic; this message just
indicates that the system doesn't know you're safe.

On the other hand, if you haven't ...

> 2) Will a full database vacuum fix the problem?

If it's fixable. I would recommend that you do this IMMEDIATELY,
rather than dithering, as every transaction you execute is taking
you one step closer to disaster.

> 3) Can it make things worse?
> 4) Other than dump and restore, what options do we have?

If you can conveniently take a full dump, that might give you some
measure of protection, but I'm not sure. I think that if there is
anything that's already wrapped around, pg_dump will not see it :-(

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-07-06 19:10:40 Re: 7.3.2 closing connections, sometimes
Previous Message Marc Munro 2005-07-06 18:45:04 Transaction id wraparound questions