| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Bernd Helmle <mailings(at)oopsware(dot)de>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Subject: | Re: "pgstat wait timeout" warnings |
| Date: | 2011-08-11 14:30:11 |
| Message-ID: | 23623.1313073011@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
>> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>> <heikki(dot)linnakangas(at)enterprisedb(dot)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.
> Yes, I have seen it several times as well. I can actually reproduce it
> without much problems, so if you have some idea to test...
It doesn't surprise me that it's possible to reproduce it under extreme
I/O load. What I am wondering about is whether there's some bug/effect
that allows it to happen without that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-08-11 14:39:19 | Re: "pgstat wait timeout" warnings |
| Previous Message | Andrew Dunstan | 2011-08-11 14:19:08 | Re: compiling 9.2 : WinXp+mingw |