Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id B32091337B6E for ; Wed, 16 Feb 2011 10:56:04 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 50945-02 for ; Wed, 16 Feb 2011 14:55:59 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mail.postgresql.org (Postfix) with ESMTP id A0C031337B34 for ; Wed, 16 Feb 2011 10:55:56 -0400 (AST) Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MURVP-1PfzjD1i31-00RLUI; Wed, 16 Feb 2011 15:55:41 +0100 Message-ID: <4D5BE56B.4030307@2ndquadrant.com> Date: Wed, 16 Feb 2011 09:55:39 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Kevin Grittner CC: pgsql-performance@postgresql.org, Verteiler_A-Team , bm@turtle-entertainment.de, Felix Feinhals , tp@turtle-entertainment.de Subject: Re: high user cpu, massive SELECTs, no io waiting problem References: <4D5A6C60020000250003AA98@gw.wicourts.gov> <4D5B7DC2.6030807@2ndquadrant.com> <4D5B8CCC020000250003AAFD@gw.wicourts.gov> In-Reply-To: <4D5B8CCC020000250003AAFD@gw.wicourts.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:ADHA+NjmCrn/oF6w/oW41SYvCzLXrTjqgy1JSKUTSFG lhAwMAOtMrwfqHEADrweiykLQm6JrW7sNptK3ADRYUYu1NbMBt JiTGLvi1UDiHFwLZB/pEhwD3CK/qM1KcVsGi6DtPt5HpbDQU6T SkR7ksr3oGfUzJMmqWXDXcalzpujV26pzDq+Us8fbFAcLH1kL9 nsvL0V7OmiEG/cI3MhK+Fbj+5MPTtldAwPZ3f9HfL8= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201102/408 X-Sequence-Number: 42546 Kevin Grittner wrote: > 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. I pulled some of them out only because they're not really postgresql.conf settings; lc_collate and lc_ctype for example are set at initdb time. Feel free to hack on that example if you feel it could be improved, just be aware which of those things are not really in the main config file when pondering if they should be included. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books