From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Stats processor not restarting |
Date: | 2007-03-20 12:48:30 |
Message-ID: | 20070320124830.GN24234@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-03-20 13:24:26 | Re: Buildfarm feature request: some way to track/classify failures |
Previous Message | Alvaro Herrera | 2007-03-20 12:42:08 | Re: Stats for multi-column indexes |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-03-20 14:50:33 | Re: Stats processor not restarting |
Previous Message | Magnus Hagander | 2007-03-20 11:23:50 | Stats processor not restarting |