Re: transaction ID wraparound - should I use 'VACUUM' or 'VACUUM FULL' ?

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Michal Szymanski <dyrex(at)poczta(dot)onet(dot)pl>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: transaction ID wraparound - should I use 'VACUUM' or 'VACUUM FULL' ?
Date: 2009-10-09 23:39:14
Message-ID: 20091009233914.GJ5303@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michal Szymanski wrote:
> Hi,
> In old version of Postgres we have to execute 'VACUUM FULL' to solve
> problem of transaction ID wraparound, do we need to execute 'VACUUM
> FULL' in Postgres 8.3 or 8.4 to avoid this problem?

No, plain VACUUM suffices.

> How to check using SQL if transaction ID is close to wraparound?

See age(datfrozenxid) FROM pg_database, but ignore system databases.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-10-10 02:11:39 Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans
Previous Message Alvaro Herrera 2009-10-09 23:37:13 Re: Regexp confusion