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

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: mlaks <mlaks(at)bellatlantic(dot)net>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters
Date: 2003-05-08 18:40:33
Message-ID: 20030508184033.GA3731@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, May 08, 2003 at 14:10:52 -0400,
mlaks <mlaks(at)bellatlantic(dot)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.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jeff Boes 2003-05-08 19:17:10 SET STATISTICS value recorded where?
Previous Message mlaks 2003-05-08 18:39:08 Re: Postgresql goes down need to restart (redhat postgresql service script) lock files removal avoid 2 postmasters