From: Laszlo Nagy <gandalf@shopzeus.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-admin@postgresql.org
Subject: Re: rebellious pg stats collector (reopened case)
Date: Mon, 29 Dec 2008 09:06:51 +0100
Message-ID: <4958851B.8060500@shopzeus.com> (raw)
In-Reply-To: <7117.1229952970@sss.pgh.pa.us>
References: <49479876.8040607@shopzeus.com>
<20081216134542.GH4741@alvh.no-ip.org>
<494B614C.5060808@shopzeus.com>
<20081219130446.GC4278@alvh.no-ip.org>
<494F67D2.3090406@shopzeus.com>
<6938.1229952228@sss.pgh.pa.us>
<20081222132721.GC10220@alvh.no-ip.org>
<7117.1229952970@sss.pgh.pa.us>
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
>
>> Tom Lane wrote:
>>
>>> I wonder whether your tracing tool is affecting the result of
>>> getppid(). Most people would consider that a bug in the tracing tool.
>>>
>
>
I wrote to an official the FreeBSD list about this getppid() problem but
got no answer other than that "this behaviour is documented". :-(
The problem is still there:
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
COMMAND
11205 pgsql 1 104 0 22400K 7112K CPU5 5 159.7H 99.02%
postgres
100% CPU since 159 hours! What can I do? Instead of tracing system
calls, is there a way to start the stats collector in debug mode? Or
maybe is it possible to change the source code, and disable the "is
postmaster alive" check for testing?
Thanks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gandalf@shopzeus.com, tgl@sss.pgh.pa.us, pgsql-admin@postgresql.org
Subject: Re: rebellious pg stats collector (reopened case)
In-Reply-To: <4958851B.8060500@shopzeus.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox