Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 39AC064FE7B
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Fri, 12 Dec 2008 13:28:21 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 13927-07
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Fri, 12 Dec 2008 13:28:09 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from gwmta.wicourts.gov (gwmta.wicourts.gov [165.219.244.99])
	by mail.postgresql.org (Postfix) with ESMTP id 2A5626501AB
	for <pgsql-hackers@postgresql.org>;
	Fri, 12 Dec 2008 13:28:09 -0400 (AST)
Received: from Courts-MTA by gwmta.wicourts.gov
	with Novell_GroupWise; Fri, 12 Dec 2008 11:28:07 -0600
Message-Id: <49424ABE.EE98.0025.0@wicourts.gov>
X-Mailer: Novell GroupWise Internet Agent 7.0.3 
Date: Fri, 12 Dec 2008 11:27:59 -0600
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Robert Haas" <robertmhaas@gmail.com>
Cc: "Josh Berkus" <josh@agliodbs.com>,
	"jd@commandprompt.com" <jd@commandprompt.com>,
	"Gregory Stark" <stark@enterprisedb.com>,
	"Nathan Boley" <npboley@gmail.com>,
	"Vladimir Sitnikov" <sitnikov.vladimir@gmail.com>,
	"Greg Smith" <gsmith@gregsmith.com>,
	<pgsql-hackers@postgresql.org>,"Tom Lane" <tgl@sss.pgh.pa.us>
Subject: Re: benchmarking the query planner
References: <603c8f070812061019r5aca3aajeaa5493b11c5feff@mail.gmail.com>
	<1d709ecc0812111354m2f5a7ba5gebc9e1d50b9de913@mail.gmail.com>
	<12251.1229034420@sss.pgh.pa.us>
	<1d709ecc0812111447m7b48bf4eg1b74e454ee3e7b7b@mail.gmail.com>
	<6fa3b6e20812111612m74555e44sfd3ef0ce5431ea9d@mail.gmail.com>
	<14209.1229041816@sss.pgh.pa.us>
	<6fa3b6e20812111735s193b4d70lb2864abf279ede9b@mail.gmail.com>
	<15086.1229046610@sss.pgh.pa.us>
	<6fa3b6e20812111839l29b851e7v409470aee8ed7785@mail.gmail.com>
	<49423C06.EE98.0025.0@wicourts.gov>
	<603c8f070812120835x7a6b7588icdf6e876239a80d1@mail.gmail.com>
In-Reply-To: <603c8f070812120835x7a6b7588icdf6e876239a80d1@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200812/963
X-Sequence-Number: 129592

>>> "Robert Haas" <robertmhaas@gmail.com> wrote: 
>>  Which raises the issue, if we could get better statistics by
passing
>> the whole table, why not do that when VACUUM ANALYZE is run?
> 
> I think the reason is "because the next autovacuum would undo it".
 
The table has 32.4 million rows.
autovacuum_analyze_scale_factor is 0.1.
autovacuum_vacuum_scale_factor is 0.2.
We run a nightly VACUUM ANALYZE.
Deletes are rare.
Normal operations don't update more than a few thousand rows per day.
 
I know that normal operations never cause an autovacuum of this table.
Perhaps if there was a way to share this information with
PostgreSQL....
 
-Kevin