Need help on autovacuum in postgres 9.1.2 - Mailing list pgsql-general

From Khangelani Gama
Subject Need help on autovacuum in postgres 9.1.2
Date
Msg-id 90aa19cfa35801aff856f6174a6fc493@mail.gmail.com
Whole thread Raw
Responses Re: Need help on autovacuum in postgres 9.1.2  (Craig Ringer <ringerc@ringerc.id.au>)
Re: Need help on autovacuum in postgres 9.1.2  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Re: Need help on autovacuum in postgres 9.1.2  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general

Hi

 

I need help in turning off autovacuum in the Database that’s running postgres 9.1.2 DB. I tried to turn it off by putting “off” in postgresql.cont file and restarted the postmaster but when I run “show autovacuum; “ query I still see autovacuum set on inside the database.

 

autovacuum

------------

on

(1 row)

 

 

postgresql.conf currently looks as follows. Should I remove the hash sign that’s before “autovacuum = off”    ?               

 

 

 

 

#autovacuum = off                       # Enable autovacuum subprocess?  'on'

#log_autovacuum_min_duration = -1       # -1 disables, 0 logs all actions and

#autovacuum_max_workers = 3             # max number of autovacuum subprocesses

#autovacuum_naptime = 1min              # time between autovacuum runs

#autovacuum_vacuum_threshold = 50       # min number of row updates before

#autovacuum_analyze_threshold = 50      # min number of row updates before

#autovacuum_vacuum_scale_factor = 0.2   # fraction of table size before vacuum

#autovacuum_analyze_scale_factor = 0.1  # fraction of table size before analyze

#autovacuum_freeze_max_age = 200000000  # maximum XID age before forced vacuum

#autovacuum_vacuum_cost_delay = 20ms    # default vacuum cost delay for

                                        # autovacuum, in milliseconds;

#autovacuum_vacuum_cost_limit = -1      # default vacuum cost limit for

                                        # autovacuum, -1 means use

 

 

 

Please assist.

 

 

 

Thanks

 

 

 

 

 

 

C O N F I D E N T I A L I T Y   N O T I C E
The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by anyone other than the intended addressee is prohibited. If you are not the intended addressee please notify the writer immediately and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no liability for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.

 




CONFIDENTIALITY NOTICE
The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by anyone other than the intended addressee is prohibited.
If you are not the intended addressee please notify the writer immediately and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no liability for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: String comparision in PostgreSQL
Next
From: Nicola Cisternino
Date:
Subject: Re: String comparision in PostgreSQL