FATAL: could not read statistics message - Mailing list pgsql-admin

From Alexander Stanier
Subject FATAL: could not read statistics message
Date
Msg-id 42DEB68F.9000801@egsgroup.com
Whole thread Raw
Responses Re: FATAL: could not read statistics message  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

pgsql-admin by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: Determine PG version used for initdb
Next
From: Guido Barosio
Date:
Subject: Re: can not start the postgresql, i use gentoo