Date: Fri, 31 Aug 2007 14:51:28 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Pallav Kalva <pkalva@livedatagroup.com>
Cc: pgsql-performance@postgresql.org, Mark Lewis <mark.lewis@mir3.com>
Subject: Re: 8.2 Autovacuum BUG ?
Message-ID: <20070831185128.GM8046@alvh.no-ip.org>
References: <46D83427.60001@livedatagroup.com>
 <25038.1188574775@sss.pgh.pa.us>
	<46D83C50.3040409@livedatagroup.com>
	<20070831161158.GD8046@alvh.no-ip.org>
	<46D840EC.1060302@livedatagroup.com>
	<1188577771.22730.238.camel@archimedes>
	<46D86103.6060204@livedatagroup.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46D86103.6060204@livedatagroup.com>
User-Agent: Mutt/1.5.16 (2007-06-11)

Pallav Kalva wrote:

> My main concern is filling up my disk with archive logs, so from all the 
> replies I get is that since tuples are already frozen, next time when it 
> runs autovacuum it wont generate any archive logs.
>
> Is my assumption right ?

Well, it won't generate any logs for the tuples that were just frozen,
but it will generate logs for tuples that weren't frozen.  How many of
these there are, depends on how many tuples you inserted after the batch
that was just frozen.

If you want to freeze the whole table completely, you can you VACUUM
FREEZE.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support