| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| 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 15:51:04 |
| Message-ID: | 14392.1174405864@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> 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?
Not really, but maybe it would be sensible to reset last_pgstat_start_time
when doing a database-wide restart? The motivation for the timeout was
to reduce cycle wastage if pgstat crashed by itself, but when you've
deliberately SIGQUITed it, that hardly seems to apply ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-20 15:59:01 | Re: Buildfarm feature request: some way to track/classify failures |
| Previous Message | Hannu Krosing | 2007-03-20 15:43:43 | Re: modifying the tbale function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-20 16:12:45 | Re: Win32 shmem |
| Previous Message | Tom Lane | 2007-03-20 15:23:11 | Re: Stats processor not restarting |