Skip site navigation (1) Skip section navigation (2)

Re: rebellious pg stats collector (reopened case)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Laszlo Nagy <gandalf(at)shopzeus(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: rebellious pg stats collector (reopened case)
Date: 2008-12-22 13:23:48
Message-ID: 6938.1229952228@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-performance
Laszlo Nagy <gandalf(at)shopzeus(dot)com> writes:
> And the stats collector exited! It cannot be by accident. Last time I 
> checked, it had the same problem: tried to poll something. It was in an 
> inifinte loop, polling something but always got POLERR. Then because I 
> started to trace it, it exited with rval=0 or rval=1.

> I do not understand why it exited after I started to trace it? Is this 
> some kind of bug?

AFAICS, the only ways to reach the exit(0) in PgstatCollectorMain are
(1) need_exit becomes set (and the only way for that to happen is
to receive a SIGQUIT signal); or (2) PostmasterIsAlive(true) fails,
which implies that getppid() is returning something different than it
used to.

I wonder whether your tracing tool is affecting the result of
getppid().  Most people would consider that a bug in the tracing tool.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Alvaro HerreraDate: 2008-12-22 13:27:21
Subject: Re: rebellious pg stats collector (reopened case)
Previous:From: Laszlo NagyDate: 2008-12-22 12:54:20
Subject: Re: Slow table update

pgsql-admin by date

Next:From: Alvaro HerreraDate: 2008-12-22 13:27:21
Subject: Re: rebellious pg stats collector (reopened case)
Previous:From: Magnus HaganderDate: 2008-12-22 12:43:16
Subject: Re: publishing changelogs on pgweb

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group