| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Euler Taveira de Oliveira <euler(at)timbira(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, Martin Pitt <martin(at)piware(dot)de> |
| Subject: | Re: stopping server does not remove external_pid_file |
| Date: | 2006-06-07 03:32:53 |
| Message-ID: | 25425.1149651173@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Doesn't removing the file reduce the chances of failing to start later
> in case another postmaster already has that pid?
No, because the external pidfile has zero to do with Postgres' internal
behavior.
Personally I always thought that the external pidfile was a "feature"
we should have rejected. It can never be a particularly reliable guide
to what PG is doing, the more especially so if the program looking at it
isn't doing any cross-checking, as the OP seems not to be doing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-06-07 03:34:36 | Re: stopping server does not remove external_pid_file |
| Previous Message | Bruce Momjian | 2006-06-07 03:25:43 | Re: stopping server does not remove external_pid_file |