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 D5C1852B7B for ; Thu, 21 Jul 2005 11:22:34 -0300 (ADT) 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 75502-03 for ; Thu, 21 Jul 2005 14:22:26 +0000 (GMT) Received: from jupiter.egsgroup.com (jupiter.egsgroup.com [217.199.182.198]) by svr1.postgresql.org (Postfix) with ESMTP id 36BE552B78 for ; Thu, 21 Jul 2005 11:22:25 -0300 (ADT) Received: by jupiter.egsgroup.com (Postfix, from userid 65) id 7503D1C6E3; Thu, 21 Jul 2005 15:22:29 +0100 (BST) X-Scanned-By: AMaViS-ng at egsgroup.com Received: from [10.20.0.81] (unknown [217.150.127.117]) by jupiter.egsgroup.com (Postfix) with ESMTP id DE1CD178F1; Thu, 21 Jul 2005 15:22:26 +0100 (BST) Message-ID: <42DFAF5E.1040805@egsgroup.com> Date: Thu, 21 Jul 2005 15:21:18 +0100 From: Alexander Stanier User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-admin@postgresql.org Subject: Re: FATAL: could not read statistics message References: <42DEB68F.9000801@egsgroup.com> <15584.1121922834@sss.pgh.pa.us> In-Reply-To: <15584.1121922834@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200507/175 X-Sequence-Number: 18231 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 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 > > >