Aldor wrote: > 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? On 8.2 this is per table. You can check which tables need vacuum with select age(relfreezexid) from pg_class (I'm not sure if the column is relfreezexid or relfrozenxid). > 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. Yeah, this is something we are planning for 8.4. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
