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

From scott.marlowe
Subject Re: VACUUM and transaction ID wraparound
Date
Msg-id Pine.LNX.4.33.0305220848490.23585-100000@css120.ihs.com
Whole thread Raw
In response to Re: VACUUM and transaction ID wraparound  (Andrew Sullivan <andrew@libertyrms.info>)
List pgsql-general
On Wed, 21 May 2003, Andrew Sullivan wrote:

> 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.

I'm not sure if it's vacuum full or vacuum, but I do know you have to
vacuum ALL the tables in ALL your databases to prevent wrap around.

Full or not, I'm not really sure.  But I run fulls every night anyway.



pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: caching query results
Next
From: "scott.marlowe"
Date:
Subject: Re: SELECT DISTINCT ON bug?