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

From Tom Lane
Subject Re: rebellious pg stats collector (reopened case)
Date
Msg-id 7117.1229952970@sss.pgh.pa.us
Whole thread Raw
In response to Re: rebellious pg stats collector (reopened case)  (Alvaro Herrera <alvherre@commandprompt.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
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.

> Probably having a close look at the PPID column in ps or top during the
> truss run would prove this.

It's at least conceivable that the result being returned inside the
process is different from what the rest of the world sees.  What'd prove
this one way or the other is to write a trivial test program along the
lines of

    while(1) {
        sleep(1);
        printf("ppid = %d\n", getppid());
    }

and see if its output changes when you start to trace it.

> Still, the actual problem being debugged is something else.

Agreed, but we need to understand what the tools being used to
investigate the problem are doing ...

            regards, tom lane

pgsql-admin by date:

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