| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Stats processor not restarting |
| Date: | 2007-03-20 15:23:11 |
| Message-ID: | 13948.1174404191@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> 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.
There is code in pgstat_start that limits the frequency with which new
stats collectors can be spawned --- maybe your test case is hitting that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-20 15:28:52 | Re: Stats for multi-column indexes |
| Previous Message | Arturo Perez | 2007-03-20 15:02:30 | Re: Buildfarm feature request: some way to track/classify failures |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-20 15:51:04 | Re: Stats processor not restarting |
| Previous Message | Magnus Hagander | 2007-03-20 15:10:02 | Re: Win32 shmem |