From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Royce Ausburn <royce(dot)ml(at)inomial(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Addition of some trivial auto vacuum logging |
Date: | 2011-09-27 18:22:38 |
Message-ID: | 26806.1317147758@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Royce Ausburn <royce(dot)ml(at)inomial(dot)com> writes:
> The attached patch adds extra detail the the existing autovacuum log message that is emitted when the log_autovacuum_min_duration threshold is met, exposing the unremovable dead tuple count similar to what you get from VACUUM VERBOSE.
> Sample log output (my addition in bold):
> LOG: automatic vacuum of table "test.public.test": index scans: 0
> pages: 0 removed, 5 remain
> tuples: 0 removed, 1000 remain, 999 dead but not removable
> system usage: CPU 0.00s/0.00u sec elapsed 0.00 sec
This proposal seems rather ill-designed. In the first place, these
numbers are quite unrelated to vacuum duration, and in the second place,
most people who might need the info don't have that setting turned on
anyway.
I wonder whether it wouldn't be more helpful to have a pg_stat_all_tables
column that reports the number of unremovable tuples as of the last
vacuum. I've been known to object to more per-table stats counters
in the past on the basis of space required, but perhaps this one would
be worth its keep.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2011-09-27 18:42:26 | Re: [PATCH] Addition of some trivial auto vacuum logging |
Previous Message | Royce Ausburn | 2011-09-27 17:51:19 | [PATCH] Addition of some trivial auto vacuum logging |