Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 05B929FB6BE for ; Tue, 16 Oct 2007 22:16:09 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 77543-01 for ; Tue, 16 Oct 2007 22:15:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 49EE29FA49C for ; Tue, 16 Oct 2007 22:16:03 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9H1G1dE026071; Tue, 16 Oct 2007 21:16:01 -0400 (EDT) To: Brian Herlihy cc: Postgresql Performance Subject: Re: Vacuum goes worse In-reply-to: <866613.1260.qm@web52305.mail.re2.yahoo.com> References: <866613.1260.qm@web52305.mail.re2.yahoo.com> Comments: In-reply-to Brian Herlihy message dated "Tue, 16 Oct 2007 17:03:39 -0700" Date: Tue, 16 Oct 2007 21:16:01 -0400 Message-ID: <26070.1192583761@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/193 X-Sequence-Number: 27215 Brian Herlihy 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