From: Alexander Stanier <alexander.stanier@egsgroup.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: FATAL: could not read statistics message
Date: Thu, 21 Jul 2005 15:21:18 +0100
Message-ID: <42DFAF5E.1040805@egsgroup.com> (raw)
In-Reply-To: <15584.1121922834@sss.pgh.pa.us>
References: <42DEB68F.9000801@egsgroup.com>
<15584.1121922834@sss.pgh.pa.us>
We are on Mac OS X 10.3 (on an X-Serve G5) and we have just upgraded to
PostgreSQL 8.0.3 from 7.4.5. This problem was not evident in 7.4.5.
Regards,
Alex Stanier
Tom Lane wrote:
>Alexander Stanier <alexander.stanier@egsgroup.com> writes:
>
>
>>2005-07-20 21:24:15 BST [13299] FATAL: could not read statistics
>>message: Resource temporarily unavailable
>>
>>
>
>
>
>>Does anyone know what this means?
>>
>>
>
>It evidently means that the pgstat collector process got an EAGAIN errno
>from recv() while trying to read a stats message. While EAGAIN is
>certainly documented as a possible failure from recv(), I'm finding it
>hard to see why any kernel would return that for a read from a file that
>has just told select() it is read-ready. What platform are you on?
>Were you having better luck with an earlier PG version, and if so which?
>
> 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: alexander.stanier@egsgroup.com, tgl@sss.pgh.pa.us
Subject: Re: FATAL: could not read statistics message
In-Reply-To: <42DFAF5E.1040805@egsgroup.com>
References: <42DEB68F.9000801@egsgroup.com> <15584.1121922834@sss.pgh.pa.us> <42DFAF5E.1040805@egsgroup.com>
* 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