From: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Logging pg_autovacuum |
Date: | 2006-04-28 00:50:39 |
Message-ID: | 445166DF.3060702@calorieking.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
>> Those messages were at LOG level because otherwise it's difficult to be
>> sure from the log that autovac is running at all.
>
> OK, so what do we want to do? Clearly outputing something everytime
> pg_autovacuum touches a database isn't ideal. By default, the server
> logs should show significant events, which this is not.
>
> Do we want something output only the first time autovacuum runs?
I've considered several times proposing that I want to be able to turn
off or do something about autovacuum log messages. I just always
thought it would be rejected.
I have it set up so that I get the last few hundred lines of my postgres
logs mailed to me each day. However, most of the time I just get a few
hundred autovacuum messages. So, I had to much around with grepping out
the autovacuum lines, etc.
I personally don't see the point of there being soooo many of those
autovacuum log messages...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-04-28 02:52:57 | pgsql: Add info on pgport linking requirements. |
Previous Message | Bruce Momjian | 2006-04-27 22:28:42 | pgsql: Rewrite Solaris compiler tas() assembly routines, merge i386 and |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2006-04-28 00:52:41 | Re: Logging pg_autovacuum |
Previous Message | Jonah H. Harris | 2006-04-28 00:45:12 | Re: Summer of Code idea |