Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 56A079F9721 for ; Fri, 31 Aug 2007 12:39:41 -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 06479-05 for ; Fri, 31 Aug 2007 12:39:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A8CFD9F94DC for ; Fri, 31 Aug 2007 12:39:37 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l7VFdau8025039; Fri, 31 Aug 2007 11:39:36 -0400 (EDT) To: Pallav Kalva cc: pgsql-performance@postgresql.org Subject: Re: 8.2 Autovacuum BUG ? In-reply-to: <46D83427.60001@livedatagroup.com> References: <46D83427.60001@livedatagroup.com> Comments: In-reply-to Pallav Kalva message dated "Fri, 31 Aug 2007 11:30:47 -0400" Date: Fri, 31 Aug 2007 11:39:35 -0400 Message-ID: <25038.1188574775@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/397 X-Sequence-Number: 26527 Pallav Kalva writes: > We turned on autovacuums on 8.2 and we have a database which is read > only , it is basically a USPS database used only for address lookups > (only SELECTS, no updates/deletes/inserts). > This database has about 10gig data and yesterday autovacuum started > on this database and all of a sudden I see lot of archive logs generated > during this time, I guess it might have generated close to 3-4gig data > during this period. Probably represents freezing of old tuples, which is a WAL-logged operation as of 8.2. Is it likely that the data is 200M transactions old? regards, tom lane