Re: Vacuuming

In  postgresql.conf parameter file, there should be the following section:


#------------------------------------------------------------------------------
# AUTOVACUUM PARAMETERS
#------------------------------------------------------------------------------

autovacuum = on           # Enable autovacuum subprocess?  'on'
                                        # requires track_counts to also be on.
log_autovacuum_min_duration = 10000       # -1 disables, 0 logs all actions and
                                        # their durations, > 0 logs only
                                        # actions running at least this number
                                        # of milliseconds.
autovacuum_max_workers = 5             # max number of autovacuum subprocesses
#autovacuum_naptime = 1min              # time between autovacuum runs
#autovacuum_vacuum_threshold = 50       # min number of row updates before
                                        # vacuum
#autovacuum_analyze_threshold = 50      # min number of row updates before
                                        # analyze

On Sat, 2010-02-13 at 12:53 -0500, Frank Bax wrote:

APseudoUtopia wrote:
> On Fri, Feb 12, 2010 at 7:32 PM,  <peter@vfemail.net> wrote:
>> There's a script running on my server hosting a PostgreSQL database that does some type of vacuuming routine every Friday at 5:00 p.m.  Specifically, the script executes this command:
>>
>>     psql -d database_name -c "vacuum full verbose"
>>
>> and e-mails the verbose output to me.  Today's report today contains about 900,000 characters.
>>
>> I don't event know where to begin reading that report, interpreting what it's telling me, determining what's important, or ascertaining what's routing and unimportant.
>>
>> Can anybody give me any guidance or point me to a document that I should read to understand what the PostgreSQL vacuum does and why this is an important function and how to decipher the verbose output?
>>
> 
> You should never run VACUUM FULL on a regular basis. In fact, it's
> recommended never to use FULL.
> See: http://wiki.postgresql.org/wiki/VACUUM_FULL
> 


I can't seem to find how to start autovacuum daemon?
Once running how can I monitor its effect?

-- Mladen Gogala Sr. Oracle DBA 1500 Broadway New York, NY 10036 (212) 329-5251 www.vmsinfo.com