Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] Addition of some trivial auto vacuum logging

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: (view raw, whole thread or download thread mbox)
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

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

In response to

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-09-27 18:42:26
Subject: Re: [PATCH] Addition of some trivial auto vacuum logging
Previous:From: Royce AusburnDate: 2011-09-27 17:51:19
Subject: [PATCH] Addition of some trivial auto vacuum logging

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group