From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Stats processor not restarting |
Date: | 2007-03-20 14:50:33 |
Message-ID: | 20070320145033.GE24280@svr2.hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Tue, Mar 20, 2007 at 08:48:30AM -0400, Alvaro Herrera wrote:
> Magnus Hagander wrote:
> > I've noticed that if for example the autovacuum process dies (such as
> > with a kill -9 when testing my new shared mem implementation), only
> > autovac and bgwriter are restarted. The stats collector is terminated,
> > but not restarted. (Same goes for a regular backend, and not just
> > autovac)
> >
> > Is there a reason for this, or is it a bug?
>
> I would say it is a bug, because the comments and code in ServerLoop()
> and reaper() say different.
Bah, sorry about the noise. It was the effect of
PGSTAT_RESTART_INTERVAL.
Do we want to add some logging when we don't restart it due to repeated
failures?
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Arturo Perez | 2007-03-20 15:02:30 | Re: Buildfarm feature request: some way to track/classify failures |
Previous Message | Tom Lane | 2007-03-20 14:40:23 | Re: Buildfarm feature request: some way to track/classify failures |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-03-20 15:10:02 | Re: Win32 shmem |
Previous Message | Alvaro Herrera | 2007-03-20 12:48:30 | Re: Stats processor not restarting |