From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nigel Bishop <Nigel.Bishop@ioko.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Question about Shared memory and PG
Date: Fri, 04 Aug 2006 11:35:27 -0400
Message-ID: <29193.1154705727@sss.pgh.pa.us> (raw)
In-Reply-To: <72558D9A7573814BB4082A28843E03D4033E0897@intyodc01.uk.ioko365.com>
References: <72558D9A7573814BB4082A28843E03D4033E0897@intyodc01.uk.ioko365.com>
"Nigel Bishop" <Nigel.Bishop@ioko.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, Nigel.Bishop@ioko.com
Subject: Re: Question about Shared memory and PG
In-Reply-To: <29193.1154705727@sss.pgh.pa.us>
References: <72558D9A7573814BB4082A28843E03D4033E0897@intyodc01.uk.ioko365.com> <29193.1154705727@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox