X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id DD9269DC817 for ; Tue, 13 Dec 2005 09:24:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60954-02 for ; Tue, 13 Dec 2005 09:24:37 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from outbound.mailhop.org (outbound.mailhop.org [63.208.196.171]) by postgresql.org (Postfix) with ESMTP id 5637F9DC81D for ; Tue, 13 Dec 2005 09:24:32 -0400 (AST) Received: from ool-4350c7ad.dyn.optonline.net ([67.80.199.173] helo=[192.168.0.91]) by outbound.mailhop.org with esmtpa (Exim 4.51) id 1EmA8w-000Mt5-0U; Tue, 13 Dec 2005 08:24:34 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 67.80.199.173 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: zeut Message-ID: <439ECB16.3090703@tocr.com> Date: Tue, 13 Dec 2005 08:22:30 -0500 From: "Matthew T. O'Connor" User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: Jeff Frost CC: Ameet Kini , pgsql-admin@postgresql.org Subject: Re: pg_autovacuum log size in postgres v8.0 References: <439CBF39.3050608@zeut.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/102 X-Sequence-Number: 19822 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 >> >