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 43FE852A8A for ; Wed, 20 Jul 2005 17:28:18 -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 55748-09 for ; Wed, 20 Jul 2005 20:28:10 +0000 (GMT) Received: from jupiter.egsgroup.com (jupiter.egsgroup.com [217.199.182.198]) by svr1.postgresql.org (Postfix) with ESMTP id BFF5252808 for ; Wed, 20 Jul 2005 17:28:09 -0300 (ADT) Received: by jupiter.egsgroup.com (Postfix, from userid 65) id A792C19DFA; Wed, 20 Jul 2005 21:28:09 +0100 (BST) X-Scanned-By: AMaViS-ng at egsgroup.com Received: from [192.168.0.2] (i-195-137-2-66.freedom2surf.net [195.137.2.66]) by jupiter.egsgroup.com (Postfix) with ESMTP id D23211865B for ; Wed, 20 Jul 2005 21:28:06 +0100 (BST) Message-ID: <42DEB68F.9000801@egsgroup.com> Date: Wed, 20 Jul 2005 21:39:43 +0100 From: Alexander Stanier Reply-To: alexander.stanier@egsgroup.com User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: FATAL: could not read statistics message 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/166 X-Sequence-Number: 18222 We have been getting the following message in our log file since upgrading to 8.0.3: 2005-07-20 21:24:15 BST [13299] FATAL: could not read statistics message: Resource temporarily unavailable Does anyone know what this means? The message seems to occur once every minute. We have the following runtime statistics in our postgresql.conf # - Statistics Monitoring - #log_parser_stats = false #log_planner_stats = false #log_executor_stats = false #log_statement_stats = false # - Query/Index Statistics Collector - #stats_start_collector = true stats_command_string = true #stats_block_level = false #stats_row_level = false #stats_reset_on_server_start = true Also I notice that pg_stat_activity does not appear to refresh when I query it to monitor current activity. I wonder if this is related? Regards, Alex Stanier.