Skip site navigation (1) Skip section navigation (2)

Re: Aggressive autovacuuming ?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Jesper Krogh <jesper(at)krogh(dot)cc>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Aggressive autovacuuming ?
Date: 2010-06-23 17:58:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Sun, Jun 20, 2010 at 4:13 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>> The largest consequence I can see at the moment is that when I get a
>> full vacuum (for preventing transaction-id wraparound) it would be
> I assume you mean the automatic database wide vacuum.  I don't think
> 8.4 and above need that anymore.  I thnk 8.3 does that too, but I'm
> not 100% sure.

8.4 (and 9.0) do still need to do vacuums to freeze tuples before
transaction ID wraparound occurs.  This is not to be confused with
VACUUM FULL, which is something else altogether.

Robert Haas
The Enterprise Postgres Company

In response to


pgsql-performance by date

Next:From: Scott MarloweDate: 2010-06-23 18:20:46
Subject: Re: Aggressive autovacuuming ?
Previous:From: Kevin GrittnerDate: 2010-06-23 17:43:15
Subject: Re: cpu bound postgresql setup.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group