Re: rebellious pg stats collector (reopened case) - Mailing list pgsql-admin

From Alvaro Herrera
Subject Re: rebellious pg stats collector (reopened case)
Date
Msg-id 20081219130446.GC4278@alvh.no-ip.org
Whole thread Raw
In response to Re: rebellious pg stats collector (reopened case)  (Laszlo Nagy <gandalf@shopzeus.com>)
Responses Re: rebellious pg stats collector (reopened case)  (Laszlo Nagy <gandalf@shopzeus.com>)
Re: rebellious pg stats collector (reopened case)  (Laszlo Nagy <gandalf@shopzeus.com>)
List pgsql-admin
Laszlo Nagy wrote:
> Alvaro Herrera wrote:
>> Laszlo Nagy wrote:
>>
>>> PostgreSQL 8.3.5, the system is now stable (uptime > 10 days).
>>> PostgreSQL stats collector uses 100% CPU forever:
>>>
>>
>> Could you grab a few stack traces from it and post them?  Also possibly
>> useful, leave strace running on the pgstat process for a while and post
>> the output somewhere.
>>
> Very interesting results. Before I used 'truss' on the process, it was:
>
> 78816 pgsql            1 106    0 22400K  7100K CPU6   6  24.2H 99.02%
> postgres
>
> After I started "truss -p 78815" the first message I got was:

It was 78816 and you traced 78815?  Are you sure the process with 24h of
CPU was pgstat?

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

pgsql-admin by date:

Previous
From: Laszlo Nagy
Date:
Subject: Re: rebellious pg stats collector (reopened case)
Next
From: Laszlo Nagy
Date:
Subject: Re: rebellious pg stats collector (reopened case)