Skip site navigation (1) Skip section navigation (2)

Re: BUG #5526: postgre can't start because of .s.PGSQL.5432.lock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "ufo008ahw" <ufo008ahw(at)163(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5526: postgre can't start because of .s.PGSQL.5432.lock
Date: 2010-06-28 13:28:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"ufo008ahw" <ufo008ahw(at)163(dot)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

In response to

pgsql-bugs by date

Next:From: Saneesh ApteDate: 2010-06-29 02:05:55
Subject: JDBC: 2 bugs: Getting a smallint array actually gets an integer array and return type of a boolean array is bit.
Previous:From: Magnus HaganderDate: 2010-06-28 13:02:59
Subject: Re: BUG #5527: Website escapes way too much

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group