Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 6A59F9F9ADC for ; Fri, 31 Aug 2007 15:42:32 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 53013-01 for ; Fri, 31 Aug 2007 15:42:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail1.livedatagroup.com (mail1.livedatagroup.com [216.154.205.166]) by postgresql.org (Postfix) with ESMTP id 9F8209FB320 for ; Fri, 31 Aug 2007 15:42:21 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mail1.livedatagroup.com (Postfix) with ESMTP id 17DDDB5D5B; Fri, 31 Aug 2007 14:42:16 -0400 (EDT) Received: from mail1.livedatagroup.com ([192.168.3.224]) by localhost (mail1.livedatagroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01103-08; Fri, 31 Aug 2007 14:42:13 -0400 (EDT) Received: from [192.168.2.134] (adsl-074-228-048-194.sip.bct.bellsouth.net [74.228.48.194]) by mail1.livedatagroup.com (Postfix) with ESMTP id B123CB5C87; Fri, 31 Aug 2007 14:42:12 -0400 (EDT) Message-ID: <46D86103.6060204@livedatagroup.com> Date: Fri, 31 Aug 2007 14:42:11 -0400 From: Pallav Kalva User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: pgsql-performance@postgresql.org CC: Mark Lewis Subject: Re: 8.2 Autovacuum BUG ? 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> In-Reply-To: <1188577771.22730.238.camel@archimedes> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at livedatagroup.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/404 X-Sequence-Number: 26534 Mark Lewis wrote: > On Fri, 2007-08-31 at 12:25 -0400, Pallav Kalva wrote: > >> Can you please correct me if I am wrong, I want to understand how this >> works. >> Based on what you said, it will run autovacuum again when it passes 200M >> transactions, as SELECTS are transactions too and are going on these >> tables. >> But the next time when it runs autovacuum, it shouldnt freeze the tuples >> again as they are already frozen and wont generate lot of archive logs ? >> Or is this because of it ran autovacuum for the first time on this db ? >> just the first time it does this process ? >> > > That is correct. The tuples are now frozen, which means that they will > not need to be frozen ever again unless you insert/update any records. > > 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 ? Thanks! everybody on all your replies. It's was very helpful. > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org >