Re: stopping server does not remove external_pid_file

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:34:36
Message-ID: 200606070334.k573YaE29100@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> 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.

Oh, it is the "external" file, not the one we automatically create in the
/data directory.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2006-06-07 13:13:15 Re: reindexdb command utlility
Previous Message Tom Lane 2006-06-07 03:32:53 Re: stopping server does not remove external_pid_file