From: | Ertan Küçükoğlu <ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Repeating autovacuum |
Date: | 2017-04-07 23:33:05 |
Message-ID: | DDB88FC4-A773-4D39-8507-5929B106DC81@1nar.com.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On 8 Apr 2017, at 01:53, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>> On Fri, Apr 7, 2017 at 3:35 PM, Ertan Küçükoğlu <ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr> wrote:
>
>> No autovacuum parameters are changed or used. They are all remarked as in
>> default config file.
>>
>> I wonder if that is a normal behavior as system is idle.
>
> See "autovacuum_naptime (integer)"
>
> https://www.postgresql.org/docs/current/static/runtime-config-autovacuum.html
>
> Its "auto" vacuum which means it runs (nearly) continuously looking for things to do.
>
> I suppose that in theory it could operate in a kind of "wait/notify" mode where every DDL against the database wakes the daemon otherwise it stays asleep. I recall some work being done a number of years back on making the system more energy efficient during no-activity periods - but there are trade-offs to consider here for which I am not up-to-speed on the specifics.
>
> It would be interesting to see the timestamps on those log entries...
>
> David J.
>
I don't see any timestamp in the log. I myself wanted that, too. Do I need to turn some switch on?
Ertan Küçükoğlu
From | Date | Subject | |
---|---|---|---|
Next Message | stevenchang1213 | 2017-04-07 23:43:45 | Re: How do you manage cluster replication and failover ? |
Previous Message | David G. Johnston | 2017-04-07 22:53:03 | Re: Repeating autovacuum |