Re: pg_ctl restart - behaviour based on wrong instance - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_ctl restart - behaviour based on wrong instance
Date
Msg-id AANLkTikDFj+2kWNPJ+v38HWv9q_J1RXaN_QPf4vghx7M@mail.gmail.com
Whole thread Raw
In response to pg_ctl restart - behaviour based on wrong instance  ("Erik Rijkers" <er@xs4all.nl>)
Responses Re: pg_ctl restart - behaviour based on wrong instance
List pgsql-hackers
On Fri, Mar 18, 2011 at 1:19 PM, Erik Rijkers <er@xs4all.nl> wrote:
> This is OK and expected.  But then it continues (in the logfile) with:
>
> FATAL:  lock file "postmaster.pid" already exists
> HINT:  Is another postmaster (PID 20519) running in data directory
> "/var/data1/pg_stuff/pg_installations/pgsql.vanilla_1/data"?
>
> So, complaints about the *other* instance.  It doesn't happen once a successful start (with pg_ctl
> start) has happened.

I'm guessing that leftover postmaster.pid contents might be
responsible for this?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Next
From: Robert Haas
Date:
Subject: Re: pg_last_xact_replay_timestamp meaning