Re: VACUUM and transaction ID wraparound - Mailing list pgsql-general

From Tom Lane
Subject Re: VACUUM and transaction ID wraparound
Date
Msg-id 17100.1053612677@sss.pgh.pa.us
Whole thread Raw
In response to Re: VACUUM and transaction ID wraparound  (Andrew Sullivan <andrew@libertyrms.info>)
Responses Re: VACUUM and transaction ID wraparound  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
Andrew Sullivan <andrew@libertyrms.info> writes:
> On Sat, May 17, 2003 at 02:34:19PM +1000, Martijn van Oosterhout wrote:
>> I beleive they are referring to the difference between VACUUM and VACUUM
>> FULL. The former is faster and doesn't lock tables, but the latter is
>> required to solve transaction wraparound.

> It is?  I didn't think VACUUM FULL was ever required.

Either one will get the job done as far as avoiding wraparound goes.
If there's someplace in the docs that seems to you to give a different
impression, please tell me where.

            regards, tom lane

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: "IN" statement causing execution cancel?
Next
From: Thomas Beutin
Date:
Subject: Re: compiling mod_auth_pgsql