Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 192111337B34
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 16 Feb 2011 10:37:49 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 12679-01
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Wed, 16 Feb 2011 14:37:41 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99])
	by mail.postgresql.org (Postfix) with ESMTP id 22B8C133616B
	for <pgsql-performance@postgresql.org>;
	Wed, 16 Feb 2011 10:37:40 -0400 (AST)
Received: from Courts-MTA by gw.wicourts.gov
	with Novell_GroupWise; Wed, 16 Feb 2011 08:37:40 -0600
Message-Id: <4D5B8CCC020000250003AAFD@gw.wicourts.gov>
X-Mailer: Novell GroupWise Internet Agent 8.0.1 
Date: Wed, 16 Feb 2011 08:37:32 -0600
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Greg Smith" <greg@2ndquadrant.com>
Cc: <pgsql-performance@postgresql.org>,
	"Verteiler_A-Team" <a-team@turtle-entertainment.de>,
	<bm@turtle-entertainment.de>,
	"Felix Feinhals" <ff@turtle-entertainment.de>, <tp@turtle-entertainment.de>
Subject: Re: high user cpu, massive SELECTs, no io waiting	
	 problem
References: 
 <F1CD4AC5B4A5024AAB60E28A82A8450A03CEB0C7@winexch1.office.turtle-entertainment.de>
	<4D5A6C60020000250003AA98@gw.wicourts.gov>
	<4D5B7DC2.6030807@2ndquadrant.com>
In-Reply-To: <4D5B7DC2.6030807@2ndquadrant.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-Spam-Status: No, hits=-4.21 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201102/407
X-Sequence-Number: 42545

Greg Smith <greg@2ndquadrant.com> wrote:
 
> I just added a sample query to provide the data we always want
> here without people having to edit their config files, by
> querying pg_settings for it, to
> http://wiki.postgresql.org/wiki/Server_Configuration
 
Nice!  Thanks!
 
A few very nice things about this:
 
(1) You don't need rights to the postgresql.conf file; any user can
run this.
 
(2) You don't need to know how to strip the comments with sed or
perl or something, or go through the file with tedious manual
editing.
 
(3) It shows some things which aren't coming from the
postgresql.conf file which might be of interest.
 
In fact, I wonder whether we shouldn't leave a couple items you've
excluded, since they are sometimes germane to problems posted, like
lc_collate and TimeZone.
 
-Kevin