From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brian Herlihy <btherl@yahoo.com.au>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Vacuum goes worse
Date: Tue, 16 Oct 2007 21:16:01 -0400
Message-ID: <26070.1192583761@sss.pgh.pa.us> (raw)
In-Reply-To: <866613.1260.qm@web52305.mail.re2.yahoo.com>
References: <866613.1260.qm@web52305.mail.re2.yahoo.com>
Brian Herlihy <btherl@yahoo.com.au> writes:
> Would it make sense to show the FSM stats for individual table vaccums as w=
> ell? I'm wondering if the reason they aren't shown is because it wouldn't =
> be useful or isn't practical, or just that it hasn't been done.
It was intentionally omitted in the original design, on the grounds that
after a single-table VACUUM there's no very good reason to think that
the global FSM stats are sufficiently complete to be accurate. Of
course, in a multi-database installation the same charge could be
leveled against the situation after a single-database VACUUM, so maybe
there's not a lot of strength in the argument.
IIRC the code change would be trivial, it's just a matter of judgment
whether the extra output is useful/trustworthy.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, btherl@yahoo.com.au
Subject: Re: Vacuum goes worse
In-Reply-To: <26070.1192583761@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox