--On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> So my theory is that if the I/O is really busy, write() on the stats file
> blocks for more than 5 seconds, and you get the timeout.
I've seen it on customer instances with very high INSERT peak loads (several
dozens backends INSERTing/UPDATEing data concurrently). We are using a RAM disk
for stats_temp_directory now for a while, and the timeout never occured again.
--
Thanks
Bernd
