From: Alexander Stanier <alexander.stanier@egsgroup.com>
To: pgsql-admin@postgresql.org
Subject: FATAL: could not read statistics message
Date: Wed, 20 Jul 2005 21:39:43 +0100
Message-ID: <42DEB68F.9000801@egsgroup.com> (raw)
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.
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
Subject: Re: FATAL: could not read statistics message
In-Reply-To: <42DEB68F.9000801@egsgroup.com>
References: <42DEB68F.9000801@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