On Fri, Mar 18, 2011 at 1:19 PM, Erik Rijkers <er(at)xs4all(dot)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
> 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?
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2011-03-19 01:35:42|
|Subject: Re: pg_last_xact_replay_timestamp meaning|
|Previous:||From: Robert Haas||Date: 2011-03-19 01:18:13|
|Subject: Re: pgsql: Document the all-balls IPv6 address.|