From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
Cc: | Andrus <eetasoft(at)online(dot)ee>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Why pgAdmin III guru suggests VACUUM in 8.1 |
Date: | 2005-11-23 04:50:42 |
Message-ID: | 10546.1132721442@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Matthew T. O'Connor" <matthew(at)zeut(dot)net> writes:
>> LOG: autovacuum: processing database "foo"
> Also this creates a lot of noise in the log files. I think it would be
> better to downgrade this message to a NOTICE or even a DEBUG, and
> replace it with a LOG level message that states when action has taken
> place against the table.
I agree that the "processing database" message isn't too exciting, but
it seems that forcing per-table messages up to LOG level would create
even more log clutter. I could support "processing table" at level
DEBUG1 and "processing database" at DEBUG2. Or maybe we should think
harder about the idea recently mentioned of letting the autovacuum
process have its own log-level setting, separate from ordinary backends'
setting.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-23 04:56:08 | Re: Index Administration: pg_index vs. pg_get_indexdef() |
Previous Message | Rick Schumeyer | 2005-11-23 04:45:05 | tsearch2: more than one index per table? |