Re: BUG #5722: vacuum full does not update last_vacuum statistics

From: Jochen Erwied <jochen(at)pgsql(dot)erwied(dot)eu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Jochen Erwied" <jochen(at)pgsql(dot)erwied(dot)eu>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5722: vacuum full does not update last_vacuum statistics
Date: 2010-10-25 14:48:39
Message-ID: 1956079949.20101025164839@erwied.eu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Monday, October 25, 2010, 4:12:39 PM you wrote:

> "Jochen Erwied" <jochen(at)pgsql(dot)erwied(dot)eu> writes:
>> VACUUM FULL does not update statistics so display of pg_stat_user_tables is
>> wrong. A normal VACUUM updates the relevant information.

> Hmm. This is a definitional issue: what do we really mean by last_vacuum?
> I'm inclined to think that the current behavior is reasonable. VACUUM
> FULL is (still) not intended as a routine maintenance operation, and
> the point of that column is to track routine maintenance operations.

Well, when reading

http://www.postgresql.org/docs/current/static/monitoring-stats.html

then last_vacuum contains the last time of a user-initiated vacuum. There's
no distinction made what kind of vacuum was made. And IMHO even if VACUUM
FULL isn't meant for routine vacuuming, the state should be changed.

Of course the easiest way to fix this bug (or better flaw) is to change the
documentation :-)

--
Jochen Erwied | home: jochen(at)erwied(dot)eu +49-208-38800-18, FAX: -19
Sauerbruchstr. 17 | work: joe(at)mbs-software(dot)de +49-2151-7294-24, FAX: -50
D-45470 Muelheim | mobile: jochen(dot)erwied(at)vodafone(dot)de +49-173-5404164

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marcus 2010-10-25 14:50:16 BUG #5723: Can not start postgres after install
Previous Message Tom Lane 2010-10-25 14:12:39 Re: BUG #5722: vacuum full does not update last_vacuum statistics