| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Federico Di Gregorio <fog(at)initd(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1707: statistics collector starts with stats_start_collector |
| Date: | 2005-06-14 07:25:12 |
| Message-ID: | 42AE8658.7020606@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
Bruce Momjian wrote:
>>
>>If we don't have a way to check this, we'll regret it soon enough...
>>now maybe a GUC setting isn't the optimal way, but I think we need
>>*some* way besides ps. ps doesn't work remotely and I think there's
>>no simple equivalent under Windows either.
>
>
> Sure, but the GUC only reports that it thinks the stats collector
> started, not whether it is running or not. I think 'ps' is a fine way
> to tell.
Um, no such beast under win32. You can only see some postgres processes,
but can't distinguish them. We'd need some functions that examine the
pids known to the postmaster (pg_get_collector_pid, pg_get_logger_pid, ...)
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bug Finder | 2005-06-14 08:07:41 | BUG #1718: geqo_selection.c:linear() |
| Previous Message | Bruce Momjian | 2005-06-14 03:08:17 | Re: BUG #1707: statistics collector starts with stats_start_collector |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atsushi Ogawa | 2005-06-14 13:16:05 | replace_text() improvement |
| Previous Message | Neil Conway | 2005-06-14 06:49:51 | Re: plpgsql raise - parameters can be expressions |