>>> On Fri, Aug 31, 2007 at 3:10 PM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> Hmm. Do I correctly grasp the picture that you've got several Postgres
> installations on the machine and they're all booted by startup scripts?
>
> In this situation, it's actually not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Sep 01, 2007 at 12:57:35AM -0400, Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > Hm. I've come to expect the OS removing all pidfiles early at bootup.
>
> If there's a script in your system that does that, then adding Postgres
> lockfiles to
[EMAIL PROTECTED] writes:
> Hm. I've come to expect the OS removing all pidfiles early at bootup.
If there's a script in your system that does that, then adding Postgres
lockfiles to it makes all kinds of sense. Our problem as upstream
software is that this isn't something well-standardized that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Aug 31, 2007 at 02:41:47PM -0500, Kevin Grittner wrote:
[...]
> > The real question there is how come the postmaster died without removing
> > the pidfile. It's not that easy to crash the postmaster ...
>
> Well, that's not due to a bug in
>>> On Fri, Aug 31, 2007 at 3:10 PM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> Well, that's not due to a bug in PostgreSQL. We're using a buggy LDAP
>> implementation (not my call) which can crash things. The machine to
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> Well, that's not due to a bug in PostgreSQL. We're using a buggy LDAP
> implementation (not my call) which can crash things. The machine totally
> locked up after logging distress messages from that daemon, and they cycled
> power to get out of it.
>>> On Fri, Aug 31, 2007 at 2:18 PM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> It appears that when pg_ctl gets a stop request for a given directory, it l=
>> ooks for a pid file in that directory and signals that pid to
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> It appears that when pg_ctl gets a stop request for a given directory, it l=
> ooks for a pid file in that directory and signals that pid to stop. It doe=
> sn't appear to check that the pid is for a PostgreSQL postmaster running ou=
> t of the given
It appears that when pg_ctl gets a stop request for a given directory, it looks
for a pid file in that directory and signals that pid to stop. It doesn't
appear to check that the pid is for a PostgreSQL postmaster running out of the
given directory. I think it should, although on a quick scan
