Re: BUG #5526: postgre can't start because of .s.PGSQL.5432.lock - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5526: postgre can't start because of .s.PGSQL.5432.lock
Date
Msg-id 26109.1277731728@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5526: postgre can't start because of .s.PGSQL.5432.lock  ("ufo008ahw" <ufo008ahw@163.com>)
List pgsql-bugs
"ufo008ahw" <ufo008ahw@163.com> writes:
> I find .s.PGSQL.5432.lock in /tmp/, and i can't start my postgre at port
> 5432.
> Why the .s.PGSQL.5432.lock is left?

That indicates you already have a postmaster running on that port.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #5527: Website escapes way too much
Next
From: Saneesh Apte
Date:
Subject: JDBC: 2 bugs: Getting a smallint array actually gets an integer array and return type of a boolean array is bit.