Search Postgresql Archives

Re: pg_dump after transaction id wraparound failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

Attachment: signature.asc
Description: Digital signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux