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

FATAL: could not read statistics message

From: Alexander Stanier <alexander(dot)stanier(at)egsgroup(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: FATAL: could not read statistics message
Date: 2005-07-20 20:39:43
Message-ID: 42DEB68F.9000801@egsgroup.com (view raw or flat)
Thread:
Lists: pgsql-admin
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.

Responses

pgsql-admin by date

Next:From: Guido BarosioDate: 2005-07-20 21:58:06
Subject: Re: can not start the postgresql, i use gentoo
Previous:From: Jiang MaDate: 2005-07-20 20:02:42
Subject: help! I can not start postgreSQL service!

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