pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Carol Walter <walterc@indiana.edu>
To: Robert Treat <robert@omniti.com>
Cc: pgsql-admin@postgresql.org, Alvaro Herrera <alvherre@commandprompt.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Auto vacuum
Date: Thu, 19 Apr 2007 17:25:28 -0400
Message-ID: <4F459AFC-5AED-4ACE-9C01-EC23E8F8AB8F@indiana.edu> (raw)
In-Reply-To: <200704191659.44378.robert@omniti.com>
References: <DFF8F759-C7C6-4092-BCB9-C7571E1C07E9@indiana.edu>
	<20070419145320.GD8402@alvh.no-ip.org>
	<5FB3A3D2-1B25-4DEC-AC42-FB8B5B978E56@indiana.edu>
	<200704191659.44378.robert@omniti.com>

I'm not sure if we've done a reload.  I'm in an academic environment  
and our department is in a state of flux right now.  I'm in the  
process of trying to get up to speed on postgreSQL as fast as I can.   
Here is the result set from that query.

select * from pg_settings where name = 'autovacuum';
     name    | setting | unit |  category  |             
short_desc             |
extra_desc | context | vartype |       source       | min_val | max_val
------------+---------+------+------------ 
+-----------------------------------+-
-----------+---------+---------+--------------------+---------+---------
autovacuum | on      |      | Autovacuum | Starts the autovacuum  
subprocess. |
            | sighup  | bool    | configuration file |         |
(1 row)

Thank you,

Carol

On Apr 19, 2007, at 4:59 PM, Robert Treat wrote:

> On Thursday 19 April 2007 13:54, Carol Walter wrote:
>> I certainly appreciate the help you've given.  Here's what the code
>> in this part of postgresql.conf file says.
>>
>> autovacuum = on
>>
>> autovacuum_naptime = 30         # time between autovacuum runs, in  
>> secs
>> autovacuum_vacuum_threshold = 500       # min # of tuple updates  
>> before
>>                                          # vacuum
>> autovacuum_analyze_threshold = 250      # min # of tuple updates  
>> before
>>                                          # analyze
>> autovacuum_vacuum_scale_factor = 0.2    # fraction of rel size before
>>                                          # vacuum
>> autovacuum_analyze_scale_factor = 0.1   # fraction of rel size before
>>                                          # analyze
>> autovacuum_vacuum_cost_delay = -1       # default vacuum cost  
>> delay for
>>                                          # autovac, -1 means use
>>                                          # vacuum_cost_delay
>> #autovacuum_vacuum_cost_limit = -1      # default vacuum cost  
>> limit for
>>                                          # autovac, -1 means use
>>                                          # vacuum_cost_limit
>>
>
> Do you know if you have done a reload of the config files since  
> these were
> changed? Try doing a select * from pg_settings where name ~  
> 'autovacuum' to
> see what your db is currently using.
>
> -- 
> Robert Treat
> Database Architect
> http://www.omniti.com




view thread (25+ messages)  latest in thread

Message-ID: <4F459AFC-5AED-4ACE-9C01-EC23E8F8AB8F@indiana.edu>
Permalink:  ../4F459AFC-5AED-4ACE-9C01-EC23E8F8AB8F@indiana.edu/
Also on:    postgresql.org/message-id/4F459AFC-5AED-4ACE-9C01-EC23E8F8AB8F@indiana.edu

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: walterc@indiana.edu, robert@omniti.com, alvherre@commandprompt.com, tgl@sss.pgh.pa.us
  Subject: Re: Auto vacuum
  In-Reply-To: <4F459AFC-5AED-4ACE-9C01-EC23E8F8AB8F@indiana.edu>

* 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