Re: VACUUM and transaction ID wraparound

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: "Dean Gibson (DB Administrator)" <dba-sql(at)ultimeth(dot)net>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: VACUUM and transaction ID wraparound
Date: 2003-05-17 04:34:19
Message-ID: 20030517043419.GD3336@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, May 16, 2003 at 09:11:19PM -0700, Dean Gibson (DB Administrator) wrote:
> The documentation says (Admin Guide, 8.2.3), "... each database-wide VACUUM automatically delivers a warning" if individual tables need VACUUMing to prevent transaction ID wraparound.
>
> But I thought a database-wide VACUUM automatically VACUUMed each table in the database (Ref Manual, 'VACUUM'), making (at least to my way of thinking) VACUUMing an individual table unnecessary, and thus making the warning superfluous.
>
> Is there something here I don't understand?

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.

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-05-17 04:40:11 Re: VACUUM and transaction ID wraparound
Previous Message Dean Gibson (DB Administrator) 2003-05-17 04:11:19 VACUUM and transaction ID wraparound