Re: VACUUM and transaction ID wraparound

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: pgsql-general(at)postgresql(dot)org
Cc: "Dean Gibson (DB Administrator)" <dba-sql(at)ultimeth(dot)net>
Subject: Re: VACUUM and transaction ID wraparound
Date: 2003-05-21 20:57:21
Message-ID: 20030521205721.GZ17292@libertyrms.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

A

--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-05-21 21:03:14 Re: ERROR: Memory exhausted in AllocSetAlloc(188)
Previous Message Jim C. Nasby 2003-05-21 20:49:21 Re: ERROR: Memory exhausted in AllocSetAlloc(188)