X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 907889FA502 for ; Tue, 27 Jun 2006 13:49:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 63751-09 for ; Tue, 27 Jun 2006 13:49:27 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.199]) by postgresql.org (Postfix) with ESMTP id 530A99FA437 for ; Tue, 27 Jun 2006 13:49:26 -0300 (ADT) Received: by wx-out-0102.google.com with SMTP id s13so1084622wxc for ; Tue, 27 Jun 2006 09:49:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=hGTBTBSSoXU8BcPHFI6rTj23l+ZjTPMDfMUyugfILANzlXXYoJA7QTDDc4AcfxcdThh96huKYb1O2UJj1hVgBotoR90Ar755pKrriZ/VmM8zoNG3umNUq+xBFgBgyBtewSuSQxdTIgura1JZSggnIfApgi0a+5pVGnijAhbLNj8= Received: by 10.70.83.20 with SMTP id g20mr10657488wxb; Tue, 27 Jun 2006 09:49:25 -0700 (PDT) Received: by 10.70.73.15 with HTTP; Tue, 27 Jun 2006 09:49:25 -0700 (PDT) Message-ID: <1d219a6f0606270949n6d23144dr1d07ee198ff0c8fc@mail.gmail.com> Date: Tue, 27 Jun 2006 12:49:25 -0400 From: "Chris Hoover" To: "Tom Lane" Subject: Re: 8.1.3 - autovacuum question Cc: "pgsql-admin@postgresql.org" In-Reply-To: <22917.1151355796@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_103671_13273514.1151426965672" References: <1d219a6f0606261338r52b14003vc384b1701718e38c@mail.gmail.com> <22917.1151355796@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/260 X-Sequence-Number: 22222 ------=_Part_103671_13273514.1151426965672 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Are there any plans to fix this so we can see atleast the table activity ( i.e. vacuuming table x) any time soon? Thanks, Chris On 6/26/06, Tom Lane wrote: > > "Chris Hoover" writes: > > I turned on autovacuum on one of my database servers over the > weekend. I > > have been looking at the logs trying to see what it is doing. However, > all > > I see are lines like this: > > ,7674,,2006-06-26 16:31:37.650 EDT,,1,,,,LOG: autovacuum: processing > > database "postgres" > > Is there a way to tell if autovacuum is actually doing any work? As far > as > > I can see, it is running, but has not done any work. > > I think that's all you'll see at the default logging level. There are > per-table messages at DEBUG2 level ... which will enable a whole lot of > other chatter as well :-( > > regards, tom lane > ------=_Part_103671_13273514.1151426965672 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Are there any plans to fix this so we can see atleast the table activity (i.e. vacuuming table x) any time soon?

Thanks,

Chris

On 6/26/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Chris Hoover" < revoohc@gmail.com> writes:
> I turned on autovacuum on one of my database servers over the weekend.  I
> have been looking at the logs trying to see what it is doing.  However, all
> I see are lines like this:
> ,7674,,2006-06-26 16:31:37.650 EDT,,1,,,,LOG:  autovacuum: processing
> database "postgres"
> Is there a way to tell if autovacuum is actually doing any work?  As far as
> I can see, it is running, but has not done any work.

I think that's all you'll see at the default logging level.  There are
per-table messages at DEBUG2 level ... which will enable a whole lot of
other chatter as well :-(

                        regards, tom lane

------=_Part_103671_13273514.1151426965672--