Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 8EE7F632A0F
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu, 25 Mar 2010 12:44:43 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 29223-03
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu, 25 Mar 2010 15:44:32 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com
	[209.85.220.224])
	by mail.postgresql.org (Postfix) with ESMTP id 6BF41632815
	for <pgsql-performance@postgresql.org>;
	Thu, 25 Mar 2010 12:44:32 -0300 (ADT)
Received: by fxm24 with SMTP id 24so3241716fxm.3
	for <pgsql-performance@postgresql.org>;
	Thu, 25 Mar 2010 08:44:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:cc:content-type;
	bh=FgoKcE7ti3Wem1weujwiB2t3P/Yz1r7ZinuURYMZe0g=;
	b=iwhuZVbwGcKApEaPlwOkw/kWRo+QHf3Ld+eOVNeBDuNUfzKPu0Kd9HBVPE+tnhI7ap
	Ut2qC9U9yZordpdNMhxGygKEmhCLYRLwZd4CP/xc2IVog8B2ZFhlHN+10XcYajF/Ebqh
	wgSkDklhHO5jgMN3T0mkCmtAthZH1GK2Bx0NM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	b=sJFOhlthsXFJvRif2nllw+vbJocCYA38bgLIy5J/9FetAOHekfOvh3wwNnL0+DHGRC
	hivlI97At+eGvEdoPezWN9Pro6aO86Myw3aWDrBdvCb1xZlisnRgSnJW7XgcyPvU+nl1
	WNZs7hl4/kwUq7+MR0GHgOQp/eyFyZAx8UDMk=
MIME-Version: 1.0
Received: by 10.239.137.197 with SMTP id m5mr2228939hbm.62.1269531871131;
 Thu,
	25 Mar 2010 08:44:31 -0700 (PDT)
In-Reply-To: <ho8qaa$2ars$1@news.hub.org>
References: <hnjrcs$2trl$1@news.hub.org> <4B9E33AF.2020608@2ndquadrant.com>
	<ho8qaa$2ars$1@news.hub.org>
Date: Thu, 25 Mar 2010 11:44:30 -0400
Message-ID: <603c8f071003250844v4a4a1683vfc821cd99de0d998@mail.gmail.com>
Subject: Re: default_statistics_target
From: Robert Haas <robertmhaas@gmail.com>
To: Carlo Stonebanks <stonec.register@sympatico.ca>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.552 tagged_above=-10 required=5 tests=AWL=-0.812,
	BAYES_20=-0.74
X-Spam-Level: 
X-Archive-Number: 201003/318
X-Sequence-Number: 38143

On Mon, Mar 22, 2010 at 6:19 PM, Carlo Stonebanks
<stonec.register@sympatico.ca> wrote:
> Thanks for the insight. How much more of a server's resources will be
> consumed by an ANALYZE with default_statistics_target = 100?

I don't think it will be much of a problem, especially since
autovacuum will do only the tables that need it and not all the same
time.  But you can certainly try it.  Before changing the global
setting, try just changing it for one session with SET:

\timing
ANALYZE <some table>;
SET default_statistics_target = 100;
ANALYZE <same table>;
\q

...Robert