From: Aldor <aldnin@yahoo.de>
To: pgsql-admin@postgresql.org
Subject: Re: autovacuum running even when not set in config?
Date: Sun, 16 Dec 2007 21:07:40 +0100
Message-ID: <fk40j1$1vs5$1@news.hub.org> (raw)
In-Reply-To: <20071210184845.GC27126@alvh.no-ip.org>
References: <20071210183551.GA11514@nemesis.aod.cx>
<20071210184845.GC27126@alvh.no-ip.org>
Well, the database is also showing a hint when less then 9 million
transactions are available - and this hint is telling us to vacuum
the whole database.
If, vacuum the whole database, would take days (quite unsure how
many days sometimes) is it possible to find out manually which
tables originally need a vacuum or is the xid wraparound problem
database wide so we MUST vacuum the whole database?
The automatic startup of autovacuum in this cases is really good,
but we would like to manage vacuum by ourself, especially WHEN it is
running, because we have different load times on different database
servers depending on time zones and the users using it.
> It is normal if the database is in danger of Xid wraparound. (So now
> you know have been neglecting to vacuum some tables).
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: aldnin@yahoo.de
Subject: Re: autovacuum running even when not set in config?
In-Reply-To: <fk40j1$1vs5$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox