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

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

From: "ufo008ahw" <ufo008ahw(at)163(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5526: postgre can't start because of .s.PGSQL.5432.lock
Date: 2010-06-28 06:43:21
Message-ID: 201006280643.o5S6hLWp071685@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5526
Logged by:          ufo008ahw
Email address:      ufo008ahw(at)163(dot)com
PostgreSQL version: 8.4.0
Operating system:   linux
Description:        postgre can't start because of .s.PGSQL.5432.lock
Details: 

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?

Responses

pgsql-bugs by date

Next:From: MarkusDate: 2010-06-28 07:53:29
Subject: BUG #5527: Website escapes way too much
Previous:From: Tom LaneDate: 2010-06-27 21:27:42
Subject: Re: interrupted createdb leaves dirty system tables

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