From: | "Matthew T(dot) O'Connor" <matthew(at)tocr(dot)com> |
---|---|
To: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
Cc: | Ameet Kini <akini(at)cs(dot)wisc(dot)edu>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_autovacuum log size in postgres v8.0 |
Date: | 2005-12-13 13:22:30 |
Message-ID: | 439ECB16.3090703@tocr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
As Alvaro already mentioned this is fixed in 8.1 because it was
integrated into the backend and benifits from the logging features that
backend already has developed.
As for the 7.4.x & 8.0.x versions of contrib autovacuum, I don't think
there are any plans for improving it. Also, added it to your logrotate
would probably be a bad idea as it has no code to reopen it's log files
on SIGHUP nor is killing and restarting the autovacuum process a good
idea as contrib/autovacuum loses track of activity when it restarts.
Matt
Jeff Frost wrote:
> Most people running Linux would add it to their logrotate.conf or
> other log management methods.
>
>
> On Mon, 12 Dec 2005, Ameet Kini wrote:
>
>>
>> Any plans of incorporating it into a future release? How do people
>> currently deal with this problem? I wonder if this is fixed in the
>> pg_autovacuum distributed with v8.1
>>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ameet Kini | 2005-12-13 17:24:26 | Lots of postmaster processes |
Previous Message | prabhakar V | 2005-12-13 09:48:40 | Backup and clean up |