X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 1D30A9FA15C for ; Tue, 16 May 2006 14:27:37 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 09249-09 for ; Tue, 16 May 2006 14:27:29 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.207]) by postgresql.org (Postfix) with ESMTP id 35C619F9C9E for ; Tue, 16 May 2006 14:27:29 -0300 (ADT) Received: by wx-out-0102.google.com with SMTP id t12so19788wxc for ; Tue, 16 May 2006 10:27:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=KQWtHRibLKzdUfVpgrdfmqqmqWHzneYumYqTpc5FnF1DGZzFTR/PAlxHpnTgFPnXMdcF3G7T49IJgHt14U02XmmZHAgzB0hTUaDw48fWbH9ifXqP2Gn/yQb1HoSo2SpQYfFqiHLHlBqyFZ7QYzpEQ6cdL2VEtpfhuYOxsHITXSI= Received: by 10.70.33.20 with SMTP id g20mr8685879wxg; Tue, 16 May 2006 10:27:07 -0700 (PDT) Received: by 10.70.80.16 with HTTP; Tue, 16 May 2006 10:27:07 -0700 (PDT) Message-ID: <1d219a6f0605161027y190c9ba2y781b048ea5c647d9@mail.gmail.com> Date: Tue, 16 May 2006 13:27:07 -0400 From: "Chris Hoover" To: "pgsql-admin@postgresql.org" Subject: Autovacuum Question MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_86411_20155913.1147800427743" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/220 X-Sequence-Number: 21752 ------=_Part_86411_20155913.1147800427743 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline PostgreSQL 8.1.3 Question on autovacuum. autovacuum_naptime (integer) Specifies the delay between activity rounds for the autovacuum subprocess. In each round the subprocess examines one database and issues VACUUM and ANALYZE commands as needed for tables in that database. The delay is measured in seconds, and the default is 60. This option can be set at serve= r start or in the postgresql.conf file. Does this mean that each run of autovacuum will vacuum/analyze all tables that need work in the database that autovacuum is looking at? The reason I'm asking is that I have ~172 non system tables in each database, so if autovacuum only does one table per run, I don't think it will ever get caught up (since there are almost 35k tables in total). Also, with over 200 databases, does this mean that a database will only get checked once about every 3.5 hours, or does autovacuum run on the database that needs the vacuuming the most? Thanks, Chris ------=_Part_86411_20155913.1147800427743 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline PostgreSQL 8.1.3

Question on autovacuum.

autovacuum_naptime (= integer)
 Specifies the delay between activity rounds for the autov= acuum subprocess. In each round the subprocess examines one database and is= sues VACUUM and ANALYZE commands as needed for tables in that database. The= delay is measured in seconds, and the default is 60. This option can be se= t at server start or in the=20 postgresql.conf file.

Does this mean that each run of autovacuum wil= l vacuum/analyze all tables that need work in the database that autovacuum = is looking at? 

The reason I'm asking is that I have ~172 non = system tables in each database, so if autovacuum only does one table per ru= n, I don't think it will ever get caught up (since there are almost 35k tab= les in total).

Also, with over 200 databases, does this mean that a database will = only get checked once about every 3.5 hours, or does autovacuum run on the = database that needs the vacuuming the most?

Thanks,

Chris
------=_Part_86411_20155913.1147800427743--