My English is very poor, below Google Translate:
"It is possible but ... Did you see any ERROR message (s) related to
statistics
collector before those ones? "
-------
Found no other error messages related to this. Disk hardware is also normal.
According to my observation, is the process of "autovacuum launcher
process" will prompt the above error, if error, suggesting that the
number of errors is relatively fixed, 182, such as 2-182, the next
prompt serial number becomes 183-363, and then the next time on 364-544.
I Postgresql code are not familiar with, and probably looked, the "stats
collector process" process to create a "pgstat.tmp" write data, and then
rename the "pgstat.stat" atomic operations, but if "autovacuum launcher
process" is being read "pgstat.stat", "stats collector process" at a
time when the rename operation if integrated autovacuum launcher process
"read the remaining old files or new data file? Is not a problem. If it
is to solve this problem need to process synchronization mechanism to
solve. Only do not have any process to read the file being read
"pgstat.stat", this time to rename operation. This is also the
possibility of error, but the probability is very small. If you want to
completely eliminate this error, you need better synchronization mechanism.
于 2012-8-24 22:22, Euler Taveira 写道:
On 24-08-2012 00:16, she...@163.net wrote:
Maybe this is a bug.
if stats collector process don't product pg_stat_tmp/pgstat.stat file, the
autovacuum launcher process will output those WARNING message?
It is possible but... Did you see any ERROR message(s) related to statistics
collector before those ones? To solver your problem, you can remove the
pgstat.stat file that it will be created again next time server starts. Of
course, you will loose the statistics, hence remember to VACUUM ANALYZE your
cluster.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
