Skip site navigation (1) Skip section navigation (2)

Re: FATAL: could not read statistics message

From: Alexander Stanier <alexander(dot)stanier(at)egsgroup(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: FATAL: could not read statistics message
Date: 2005-07-21 14:21:18
Message-ID: 42DFAF5E.1040805@egsgroup.com (view raw or flat)
Thread:
Lists: pgsql-admin
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(dot)stanier(at)egsgroup(dot)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
>
>  
>

In response to

pgsql-admin by date

Next:From: Brad NicholsonDate: 2005-07-21 14:46:25
Subject: Re: PGSQL 7.4.8 : idle in transaction problem
Previous:From: Palle GirgensohnDate: 2005-07-21 14:08:06
Subject: Re: mirror for gborg.postgresql.org?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group