X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 281CC9FB39F for ; Fri, 4 Aug 2006 12:35:41 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 53700-05 for ; Fri, 4 Aug 2006 12:35:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2DE1B9FB1E1 for ; Fri, 4 Aug 2006 12:35:32 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k74FZRgg029194; Fri, 4 Aug 2006 11:35:27 -0400 (EDT) To: "Nigel Bishop" cc: pgsql-admin@postgresql.org Subject: Re: Question about Shared memory and PG In-reply-to: <72558D9A7573814BB4082A28843E03D4033E0897@intyodc01.uk.ioko365.com> References: <72558D9A7573814BB4082A28843E03D4033E0897@intyodc01.uk.ioko365.com> Comments: In-reply-to "Nigel Bishop" message dated "Fri, 04 Aug 2006 14:18:42 +0100" Date: Fri, 04 Aug 2006 11:35:27 -0400 Message-ID: <29193.1154705727@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.155 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200608/40 X-Sequence-Number: 22584 "Nigel Bishop" writes: > In the PG log file the errors were: > 2006-08-03 21:49:18 BST FATAL: invalid frontend message type 50 > 2006-08-03 21:49:18 BST LOG: unexpected EOF on client connection > 2006-08-03 21:49:18 BST LOG: unexpected EOF on client connection These look to me like your client(s) having a problem, not the server. Or as you say it could have been a network hiccup. I think the SHMMAX setting was unrelated, and had your operator not insisted on waving a dead chicken by rebooting the database, you'd still not know that someone had changed SHMMAX ... regards, tom lane