Re: VACUUM and transaction ID wraparound

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Sullivan <andrew(at)libertyrms(dot)info>, pgsql-general(at)postgresql(dot)org, "Dean Gibson (DB Administrator)" <dba-sql(at)ultimeth(dot)net>
Subject: Re: VACUUM and transaction ID wraparound
Date: 2003-05-22 23:33:30
Message-ID: 20030522233330.GA31575@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 22, 2003 at 10:11:17AM -0400, Tom Lane wrote:
> Andrew Sullivan <andrew(at)libertyrms(dot)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.

Sorry, must be my memory. I remember something about requiring a VACUUM FULL
at least once every two billion transactions. I must have misremembered,
sorry.
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> "the West won the world not by the superiority of its ideas or values or
> religion but rather by its superiority in applying organized violence.
> Westerners often forget this fact, non-Westerners never do."
> - Samuel P. Huntington

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ernest E Vogelsinger 2003-05-22 23:36:14 Re: [ADMIN] Q: Structured index - which one runs faster?
Previous Message Darren Ferguson 2003-05-22 23:11:50 Re: ILIKE Problem?