From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Kostis Mentzelos <mentzelos(at)gmx(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Lost databases |
Date: | 2004-11-17 11:29:48 |
Message-ID: | 20041117112944.GA25482@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Look at the documentation here:
http://www.postgresql.org/docs/7.4/interactive/maintenance.html
The upshot is that you should vacuum every table in the database at
least once every billion transaction. It doesn't have to be a VACUUM
FULL, just run VACUUM without specifying a table.
There's some info in there about how to work out when it is necessary.
Hope this helps,
On Tue, Nov 16, 2004 at 12:22:46PM +0200, Kostis Mentzelos wrote:
> Only VACUUM FULL solves XID wraparound problem? I mean VACUUM FULL locks
> the entire table.
>
> How can I test if I am close to XID wraparround?
>
> Kostis
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
From | Date | Subject | |
---|---|---|---|
Next Message | David Helgason | 2004-11-17 11:41:04 | Re: Controlling maximal on-disk size of a table |
Previous Message | Konstantin Danilov | 2004-11-17 11:09:03 | PostgreSQL certification |