On 12/29/2010 2:58 PM, Tom Lane wrote:
It happened for you on 8.4 too? In that previous thread you were still
on 8.3. If you did see it on 8.4 then it wasn't sinval ...
regards, tom lane
May I ask what exactly is "sinval"? I took a look at Craig's problem and
your des
On 12/29/10 11:58 AM, Tom Lane wrote:
Craig James writes:
On 12/29/10 6:28 AM, Julian v. Bock wrote:
I have the problem that on our servers it happens regularly under a
certain workload (several times per minute) that all backend processes
get a SIGUSR1 and spend several seconds in ProcessCatc
Craig James writes:
> On 12/29/10 6:28 AM, Julian v. Bock wrote:
>> I have the problem that on our servers it happens regularly under a
>> certain workload (several times per minute) that all backend processes
>> get a SIGUSR1 and spend several seconds in ProcessCatchupEvent().
> This sounds like
On 12/29/10 6:28 AM, Julian v. Bock wrote:
I have the problem that on our servers it happens regularly under a
certain workload (several times per minute) that all backend processes
get a SIGUSR1 and spend several seconds in ProcessCatchupEvent(). At
100-200 connections (most of them idle) this c
b...@openit.de (Julian v. Bock) writes:
> I have the problem that on our servers it happens regularly under a
> certain workload (several times per minute) that all backend processes
> get a SIGUSR1 and spend several seconds in ProcessCatchupEvent().
This is fixed in 8.4 and up.
http://archives.po
Hi
I have the problem that on our servers it happens regularly under a
certain workload (several times per minute) that all backend processes
get a SIGUSR1 and spend several seconds in ProcessCatchupEvent(). At
100-200 connections (most of them idle) this causes the system load to
skyrocket. I am
