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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Michal Szymanski <dyrex(at)poczta(dot)onet(dot)pl>, pgsql-general(at)postgresql(dot)org
Subject: Re: transaction ID wraparound - should I use 'VACUUM' or 'VACUUM FULL' ?
Date: 2009-10-10 02:38:14
Message-ID: 5224.1255142294@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Michal Szymanski wrote:
>> 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.

Just to clarify: plain VACUUM has always sufficed; in *no* version of
Postgres has it ever been the case that VACUUM FULL was more useful
than VACUUM to protect against wraparound.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-10-10 03:56:28 Re: Regexp confusion
Previous Message Tom Lane 2009-10-10 02:31:31 Re: Regexp confusion