From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | ghiureai <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca> |
Cc: | "pgsql-admin\(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: autovacuum logs question |
Date: | 2017-07-12 19:13:36 |
Message-ID: | 87bmopv57j.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
ghiureai <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca> writes:
> Hi ,
> I am running Pgsql version 9.5.6 with :
>
> autovacuum = on
> log_autovacuum_min_duration = 0
> autovacuum_naptime = 3min
>
> I was hoping to see in errorlog all the stats time and CPU usage
> for autovacumm operationfor all tables , but so far there is only
> one and same table been logged , how about rest of them, the other
> autovacuum param are disabled ( using the default values)
> Thank you
I assume autovac not visiting those tables due to insufficient churn.
Review the docs in regards to the threshold/scale settings that
determine how aggressive autovac is.
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | John Scalia | 2017-07-14 14:58:48 | synchronous_standby_name format |
Previous Message | Ashish Tiwari | 2017-07-12 15:10:26 | Re: could not access status of transaction |