Re: pg_dump after transaction id wraparound failure - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: pg_dump after transaction id wraparound failure
Date
Msg-id 20060515190155.GB23811@svana.org
Whole thread Raw
In response to Re: pg_dump after transaction id wraparound failure  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
On Mon, May 15, 2006 at 08:48:54PM +0200, Martijn van Oosterhout wrote:
> Vacuum will make anything that disappeared by wraparound in the last
> billion transactions reappear, so a databasewide vacuum should solve
> all your problems, no need to dump...

Also, for future reference. If you have a lot of read-only tables (and
judging by the names of your tables it looks like you might), then
running VACUUM FREEZE on a table will put it in a state where you never
have to vacuum it again (until you do an insert/update).

Put another way, anything in a table at the point you run a VACUUM
FREZE over it is protected from wraparound. Over time all tables will
convert to this state, just an explicit freeze makes it quicker, for a
1.4TB data this might be important.

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: pg_dump after transaction id wraparound failure
Next
From: Tom Lane
Date:
Subject: Re: pg_dump after transaction id wraparound failure