pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jaime Casanova <systemguards@gmail.com>
To: Stephen Byers <stephenabyers@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum on updated rows
Date: Fri, 11 Nov 2005 15:37:40 -0500
Message-ID: <c2d9e70e0511111237g50580d74ya0e7067b3d724e64@mail.gmail.com> (raw)
In-Reply-To: <20051111201030.68086.qmail@web30703.mail.mud.yahoo.com>
References: <20051111201030.68086.qmail@web30703.mail.mud.yahoo.com>

On 11/11/05, Stephen Byers <stephenabyers@yahoo.com> wrote:
> 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.
>
>

i will assume you change #autovacuum=off for on in postgresql.conf you
have to activet stats_stat_collector and stats_row_level too...

here explains what factors are used for determining vacuum needs for
tables: http://www.postgresql.org/docs/8.1/static/maintenance.html#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)
>
>

--
Atentamente,
Jaime Casanova
(DBA: DataBase Aniquilator ;)



view thread (5+ messages)  latest in thread

Message-ID: <c2d9e70e0511111237g50580d74ya0e7067b3d724e64@mail.gmail.com>
Permalink:  ../c2d9e70e0511111237g50580d74ya0e7067b3d724e64@mail.gmail.com/
Also on:    postgresql.org/message-id/c2d9e70e0511111237g50580d74ya0e7067b3d724e64@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: systemguards@gmail.com, stephenabyers@yahoo.com
  Subject: Re: autovacuum on updated rows
  In-Reply-To: <c2d9e70e0511111237g50580d74ya0e7067b3d724e64@mail.gmail.com>
  References: <20051111201030.68086.qmail@web30703.mail.mud.yahoo.com> <c2d9e70e0511111237g50580d74ya0e7067b3d724e64@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox