Re: How to avoid Force Autovacuum

From: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
To: Vishalakshi Navaneethakrishnan <nvishalakshi(at)sirahu(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to avoid Force Autovacuum
Date: 2013-08-08 01:29:30
Message-ID: CAL_0b1sQ4M0vNJwp+Mv63KoiLqVfYcX_wPNF+Emu9hGN59JsMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On Wed, Aug 7, 2013 at 2:46 AM, Vishalakshi Navaneethakrishnan
<nvishalakshi(at)sirahu(dot)com> wrote:
> Daily once we are executing "Vacuum Freeze analyze" -- To prevent
> transaction id wraparound
> using this command
> vacuumdb -F -z -h localhost -U postgres dbname

It is not necessary to do. Autovacuum does it itself where and when needed.

> Even sometimes autovacuum running on the databases and increase the load
> (Above 200) very much and the server was unresponsive
>
> I have seen the autovacum worker process in top command,
> While i executing pg_stat_activity as postgres user, i have seen the pid of
> autovacuum process in the result but the query filed is "Empty"

Was autovacuum the only process that you saw in pg_stat_activity?

What OS do you use?

Do you use huge pages?

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vishalakshi Navaneethakrishnan 2013-08-08 04:32:05 Re: How to avoid Force Autovacuum
Previous Message Bruce Momjian 2013-08-07 16:19:53 Re: BUG #8335: trim() un-document behaviour

Browse pgsql-general by date

  From Date Subject
Next Message liuyuanyuan 2013-08-08 01:41:25 Re: inserting huge file into bytea cause out of memory
Previous Message Kallon Weingarten 2013-08-08 00:11:14 Re: Incremental backup with RSYNC or something?