From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(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:25:43 |
Message-ID: | 200606070325.k573PhX27757@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Tom Lane wrote:
> Euler Taveira de Oliveira <euler(at)timbira(dot)com> writes:
> > Martin Pitt wrote:
> >> I just played around with external_pid_file in 8.1.4. I noticed that
> >> the file is created and filled properly, but it is not removed again
> >> when the server is stopped.
> >>
> > Looking at the code I see this comment in
> > src/backend/postmaster/postmaster.c
>
> > /* Should we remove the pid file on postmaster exit? */
>
> > IMHO, yes. It's not useful anymore.
>
> [ shrug... ] If the postmaster crashes, it would certainly fail to
> remove the pidfile. So I'd argue that your unnamed external script
> that is expecting the pidfile to go away needs work: if it's not
> verifying the PID given in the file, it's broken.
Doesn't removing the file reduce the chances of failing to start later
in case another postmaster already has that pid? Why do we keep it
around?
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-07 03:32:53 | Re: stopping server does not remove external_pid_file |
Previous Message | Tom Lane | 2006-06-07 02:52:01 | Re: stopping server does not remove external_pid_file |