Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 94E159F9D99 for ; Thu, 9 Nov 2006 02:58:31 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 37021-01-3 for ; Thu, 9 Nov 2006 06:58:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from lists.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id 0BF679F9424 for ; Thu, 9 Nov 2006 02:58:26 -0400 (AST) Received: from [192.168.1.95] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id kA96wNNu007036 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 8 Nov 2006 22:58:24 -0800 Subject: Re: statistics buffer is full From: "Joshua D. Drake" To: Jeff Frost Cc: pgsql-admin@postgresql.org In-Reply-To: References: <1163042869.28784.55.camel@localhost.localdomain> <1163043819.28784.57.camel@localhost.localdomain> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Wed, 08 Nov 2006 22:59:24 -0800 Message-Id: <1163055564.28784.59.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 08 Nov 2006 22:58:24 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/83 X-Sequence-Number: 23610 On Wed, 2006-11-08 at 21:46 -0800, Jeff Frost wrote: > On Wed, 8 Nov 2006, Joshua D. Drake wrote: > > >> hah! Does that mean it's just the buffering for pg_stat_activity and not for > >> planner statistics? That doesn't make me feel too bad in this case. > > > > Yeah it is nothing to worry about, however turning it off is certainly a > > performance benefit. > > > > So, then the next question: is that error because the command string was too > long or because there were too many command strings in the buffer at once > (i.e. it got backed up a bit and filled)? This one I can't answer. > > It would be a drag to be without pg_stat_activity on this system. The > performance detriment is lessened in 8.2, correct? Yes my understanding is work was done on 8.2 to help eliviate the issue. Sincerely, Joshua D. Drake > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate