Re: Autovacuum behavior

From: Om Prakash Jaiswal <op12om(at)yahoo(dot)co(dot)in>
To: John Scalia <jayknowsunix(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Autovacuum behavior
Date: 2015-07-31 04:44:27
Message-ID: 810264764.37549.1438317867083.JavaMail.yahoo@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

track_count = on;It is missing.

RegardsOm Prakash

On Friday, 31 July 2015 12:21 AM, John Scalia <jayknowsunix(at)gmail(dot)com> wrote:

Hi all,
The autovacuum settings for a 9.4.2 database are shown below, I'm not absolutely certain if I missed anything:
autovacuum = onlog_autovacuum_min_duration = 100autovacuum_max_workers = 15autovacuum_naptime = 10min#autovacuum_vacuum_threshold = 50autovacuum_analyze_threshold = 80autovacuum_vacuum_scale_factor = 0.1autovacuum_analyze_scale_factor = 0.2autovacuum_freeze_max_age = 100000000autovacuum_vacuum_cost_delay = 20msautovacuum_vacuum_cost_limit = -1vacuum_freeze_min_age =   5000000vacuum_freeze_table_age = 2500000

But, when I examine pg_stat_all_tables, I'm seeing a lot of tables where n_dead_tup is still a lot greater than n_live_tup. Mind you, these are all fairly small tables. I'm also seeing that the last_autovacuum ran about 11:22 AM CDT this morning.I would think the tables where there were no live tuples and a bunch of dead_tuples would have been vacuumed after 11:22 AM to clear the dead ones. Am I missing something?--Jay

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Renato Oliveira 2015-07-31 06:34:34 Re: [GENERAL] How Many PG_Locks are considered too many
Previous Message John Scalia 2015-07-30 19:13:07 Re: Autovacuum behavior