X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AB1BF3A6BFB for ; Fri, 10 Dec 2004 22:31:58 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 00422-08 for ; Fri, 10 Dec 2004 22:31:26 +0000 (GMT) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by svr1.postgresql.org (Postfix) with ESMTP id 2E41F3B33F1 for ; Fri, 10 Dec 2004 18:50:45 +0000 (GMT) Received: from ns1.turtle-entertainment.de (ns1.turtle-entertainment.de [193.41.200.20]) by svr4.postgresql.org (Postfix) with ESMTP id E590E5B147F for ; Wed, 8 Dec 2004 21:17:07 +0000 (GMT) Received: from ip96.85.1311c-cud12k-02.ish.de ([62.143.85.96] helo=mail.office.turtle-entertainment.de) by ns1.turtle-entertainment.de with asmtp (Exim 3.22 #3 (Debian)) id 1Cc9BB-0000O4-00 for ; Wed, 08 Dec 2004 22:16:57 +0100 Received: from ip19.1.1411j-cud12k-02.ish.de ([62.143.1.19] helo=[192.168.100.5]) by mail.office.turtle-entertainment.de with asmtp (Exim 3.22 #7 (Debian)) id 1Cc9BB-0001g9-00 for ; Wed, 08 Dec 2004 22:16:57 +0100 Message-ID: <41B76F00.3010804@turtle-entertainment.de> Date: Wed, 08 Dec 2004 22:15:44 +0100 From: Bjoern Metzdorf User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Pgsql-Admin (E-mail)" Subject: statistics buffer is full Content-Type: multipart/mixed; boundary="------------060103080503020603080701" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.842 tagged_above=0 required=5 tests=FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200412/69 X-Sequence-Number: 15655 This is a multi-part message in MIME format. --------------060103080503020603080701 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, just wanted to share some experience with the curious log message: "statistics buffer is full". Some time ago we suffered from bad performance on our database server. We were running 7.4.x. I saw this strange log message and Tom told me a way to raise this specific buffer. After raising it the box worked fine. Now we are running 7.4.6 and I still have to patch the source, as I had to do with all 7.4.x versions. See attached patch for details. We began raising from 1024 to 2048 then to 4096. After a while the messages appeared again and now we are at 16384 and the messages have gone again. Tom: Do you know of any other bad impact this raising might have? All: If you suffer from bad performance, check your logs and raise this buffer. Our specs: Debian Woody, Kernel 2.6 Postgresql 7.4.6 Dual Xeon 3.2 with HT enabled Mylex eXtremeRAID 2000 with 4 drives RAID 10 Regards, Bjoern --------------060103080503020603080701 Content-Type: text/plain; name="pg_buffers_full-7.4.6.patch.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pg_buffers_full-7.4.6.patch.txt" --- src/include/pgstat.h~ 2004-12-08 16:28:12.000000000 +0100 +++ src/include/pgstat.h 2004-12-08 16:28:12.000000000 +0100 @@ -65,7 +65,7 @@ * Amount of space reserved in pgstat_recvbuffer(). * ---------- */ -#define PGSTAT_RECVBUFFERSZ ((int) (1024 * sizeof(PgStat_Msg))) +#define PGSTAT_RECVBUFFERSZ ((int) (16384 * sizeof(PgStat_Msg))) /* ---------- --------------060103080503020603080701--