Re: Logging pg_autovacuum - Mailing list pgsql-hackers

From Larry Rosenman
Subject Re: Logging pg_autovacuum
Date
Msg-id F6616E0E81AC0841B1F9DD252F7C4B55041A4D@ausmaildd.aus.pervasive.com
Whole thread Raw
In response to Logging pg_autovacuum  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Logging pg_autovacuum
List pgsql-hackers
Jim C. Nasby wrote:
> On Mon, May 01, 2006 at 12:28:21PM -0500, Larry Rosenman wrote:
>> Since both vacuum and autovacuum will be cutting stats records, do we
>> want to just have the autovacuum
>> stats record have the fact that it was autovacuum that did the
>> vacuum?
>>
>> Or, is there a way when vacuum is run by autovacuum that I can get a
>> flag to set that says this (vacuum|analyze) was done by the
>> autovacuum daemon?
>>
>> I agree that the existing stats calls are good, but I'm still reading
>> code to see whether I can determine
>> at the time they are cut that this was autovacuum that did it.
>
> I think noting autovac vacuums/analyzes seperately is 'nice-to-have'
> but not all that important. It'd probably be pretty easy to tell the
> difference just knowing what (if any) manual vacuums your system runs.
>
> While we're looking at logging, are you going to add stats stuff for
> the bgwriter as well, or should we add this to the TODO?

I was going to do that after I got some comfort with what I'm doing
here.



--
Larry Rosenman
Database Support Engineer

PERVASIVE SOFTWARE. INC.
12365B RIATA TRACE PKWY
3015
AUSTIN TX  78727-6531

Tel: 512.231.6173
Fax: 512.231.6597
Email: Larry.Rosenman@pervasive.com
Web: www.pervasive.com


pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: CVSup server seems to be down
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Automatic free space map filling