On Thu, Aug 11, 2011 at 10:30 AM, Tom Lane wrote:
> Andres Freund writes:
>>> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>>> 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
Andres Freund writes:
>> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>> 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 reprodu
On Thursday, August 11, 2011 11:49:12 Bernd Helmle wrote:
> --On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
>
> 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 custome
--On 10. August 2011 21:54:06 +0300 Heikki Linnakangas
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 IN
On 10.08.2011 21:45, Tom Lane wrote:
We occasionally see $SUBJECT in the buildfarm, and I've also recently
had reports of them from Red Hat customers. The obvious theory is that
these reflect high load preventing the stats collector from responding,
but it would really take pretty crushing load
We occasionally see $SUBJECT in the buildfarm, and I've also recently
had reports of them from Red Hat customers. The obvious theory is that
these reflect high load preventing the stats collector from responding,
but it would really take pretty crushing load to make that happen if
there were not a
