X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2B819D9DD0 for ; Fri, 11 Nov 2005 16:17:12 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26121-09 for ; Fri, 11 Nov 2005 20:17:09 +0000 (GMT) X-Greylist: delayed 00:06:40.030294 by SQLgrey- Received: from web30703.mail.mud.yahoo.com (web30703.mail.mud.yahoo.com [68.142.200.136]) by svr1.postgresql.org (Postfix) with SMTP id 093B9D9DC2 for ; Fri, 11 Nov 2005 16:17:09 -0400 (AST) Received: (qmail 68088 invoked by uid 60001); 11 Nov 2005 20:10:30 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=IXDz+hD9OjyA3nQaUk2MB5aUCclMvZoAqi8X7wKtfkIrjWD2M2QJcZ5IJYMqBRzpZsiRhaJiUr77XpOMXpPTmb6F8Cjb3ZSErpkPy0R4XtqDUp5Ga1c3QxVsjnuqzeMMKcB/m5Xc8sIJWZUBsYhYdu8/WS+ZYuEqYdjQt7CamOg= ; Message-ID: <20051111201030.68086.qmail@web30703.mail.mud.yahoo.com> Received: from [216.127.142.194] by web30703.mail.mud.yahoo.com via HTTP; Fri, 11 Nov 2005 12:10:30 PST Date: Fri, 11 Nov 2005 12:10:30 -0800 (PST) From: Stephen Byers Subject: autovacuum on updated rows To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1501457849-1131739830=:68084" Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.48 required=5 tests=[DNS_FROM_RFC_ABUSE=0.479, HTML_MESSAGE=0.001] X-Spam-Score: 0.48 X-Spam-Level: X-Archive-Number: 200511/141 X-Sequence-Number: 19514 --0-1501457849-1131739830=:68084 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit I am using new postgres 8.1 and also trying out the integrated autovacuum. I have a concern. I have a table where I perform an update on a row every 10 seconds. The table is VERY small. Hardly any INSERTS, no DELETES, and a ton of UPDATES. adbs_db=# select count(*) from volumes; count ------- 7 (1 row) I am looking at the file sizes that correspond to this table and its indeces. They are growing -- I think I understand why -- dead rows are occuring on an UPDATE. But what I don't understand is why autovacuum has not kicked in-- I have kept the default values on autovacuum. In about 50 minutes' time, the table itself has grown 2MB, and each index has grown by about 1MB Will autovacuum eventually run on this table???? What rows/columns does autovacuum look at to determine when to work on a table? I'd like to look at those rows, too. Thanks!! Steve adbs_db=# \d volumes Table "public.volumes" Column | Type | Modifiers ------------------+------------------------+-------------------- label | character varying(128) | not null imported | boolean | not null closed | boolean | not null active | boolean | not null online | boolean | not null offline | boolean | not null archiver_name | character varying(32) | not null environment_name | character varying(32) | not null curr_size | bigint | not null default 0 vol_num | integer | not null start_time | integer | stop_time | integer | Indexes: "volumes_i1" unique, btree (label) "volumes_i2" btree (environment_name) --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click. --0-1501457849-1131739830=:68084 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
I am using new postgres 8.1 and also trying out the integrated autovacuum.  I have a concern.
 
I have a table where I perform an update on a row every 10 seconds.  The table is VERY small.  Hardly any INSERTS, no DELETES, and a ton of UPDATES.
 
adbs_db=# select count(*) from volumes;
 count
-------
     7
(1 row)

 

 

I am looking at the file sizes that correspond to this table and its indeces.  They are growing -- I think I understand why -- dead rows are occuring on an UPDATE.  But what I don't understand is why autovacuum has not kicked in-- I have kept the default values on autovacuum.

 

In about 50 minutes' time, the table itself has grown 2MB, and each index has grown by about 1MB

 
Will autovacuum eventually run on this table????  What rows/columns does autovacuum look at to determine when to work on a table?  I'd like to look at those rows, too.
 
Thanks!!
Steve
 
 
adbs_db=# \d volumes
                     Table "public.volumes"
      Column      |          Type          |     Modifiers     
------------------+------------------------+--------------------
 label            | character varying(128) | not null
 imported         | boolean                | not null
 closed           | boolean                | not null
 active           | boolean                | not null
 online           | boolean                | not null
 offline          | boolean                | not null
 archiver_name    | character varying(32)  | not null
 environment_name | character varying(32)  | not null
 curr_size        | bigint                 | not null default 0
 vol_num          | integer                | not null
 start_time       | integer                |
 stop_time        | integer                |
Indexes:
    "volumes_i1" unique, btree (label)
    "volumes_i2" btree (environment_name)


Yahoo! FareChase - Search multiple travel sites in one click. --0-1501457849-1131739830=:68084--