|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Andy Colson <andy(at)squeakycode(dot)net>|
|Cc:||Thom Brown <thom(at)linux(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: WARNING: pgstat waiting|
|Views:||Raw Message | Whole Thread | Download mbox|
Andy Colson <andy(at)squeakycode(dot)net> writes:
> On 09/10/2011 11:43 AM, Thom Brown wrote:
>> On 10 September 2011 17:40, Andy Colson<andy(at)squeakycode(dot)net> wrote:
>>> I'm playing with 9.2devel, and I can fill my logs with:
>>> WARNING: pgstat waiting for 5001623 usec (494 loops), file timestamp
>>> 368986878169601 target timestamp 368986897680812 last errno 0
>> I've had exactly the same sort of messages, pages of them. But wasn't
>> quite sure what I needed to recreate it.
> Just hammer a table with updates. I used:
If the machine is under heavy load, that's more or less expected. The
reason the extra messages are in there is that I wanted to see if there
was something else going on with the buildfarm machines that sometimes
show pgstat timeouts. So far it doesn't look like there are any
surprises, so I'm going to revert that commit sometime soon.
I have been thinking of increasing the pgstat timeout from 5 seconds to
10, just to cut the number of buildfarm reports. Thoughts?
regards, tom lane
|Next Message||Tom Lane||2011-09-10 17:21:19||Re: collation, arrays, and ranges|
|Previous Message||Jeff Davis||2011-09-10 16:51:12||collation, arrays, and ranges|