Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters - Mailing list pgsql-admin

From Bruno Wolff III
Subject Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters
Date
Msg-id 20030508184033.GA3731@wolff.to
Whole thread Raw
In response to Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters  (mlaks <mlaks@bellatlantic.net>)
Responses Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters
List pgsql-admin
On Thu, May 08, 2003 at 14:10:52 -0400,
  mlaks <mlaks@bellatlantic.net> wrote:
> Thank you for your response Bruno. I agree about the importance of using the
> lines
>
> #!/bin/sh
> exec 2>&1
> exec setuidgid postgres /usr/local/pgsql/bin/postmaster -D
> /usr/local/pgsql/data
>
> in the run file. However, what else must we put in as well?
>
> My question is to understand the lock files for postgresql so I can deal with
> the following:

Some of the lock files have to do with the init system. Those can be
ignored. Postgres also keeps a lock file and that is used to prevent
two postmasters from running at the same time. You probably don't want
to have a script remove that lock file, because if there really is
another postmaster running, starting a second one can be a disaster.


pgsql-admin by date:

Previous
From: mlaks
Date:
Subject: Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters
Next
From: mlaks
Date:
Subject: Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters