Re: Aggressive autovacuuming ? - Mailing list pgsql-performance

From Robert Haas
Subject Re: Aggressive autovacuuming ?
Date
Msg-id AANLkTikgxnOUQZRKOteeU2ipTqXge8f1y7ANuT3V-ozr@mail.gmail.com
Whole thread Raw
In response to Re: Aggressive autovacuuming ?  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-performance
On Wed, Jun 23, 2010 at 2:20 PM, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> On Wed, Jun 23, 2010 at 1:58 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Sun, Jun 20, 2010 at 4:13 PM, Scott Marlowe <scott.marlowe@gmail.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.
>
> My point was that modern pgsql doesn't need db wide vacuum to prevent
> wrap around anymore, but can vacuum individual relations to prevent
> wraparound.

Oh, I see.  I didn't realize we used to do that.  Looks like that
change was committed 11/5/2006.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-performance by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Aggressive autovacuuming ?
Next
From: Anj Adu
Date:
Subject: WAL+Os on a single disk