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

Re: BUG #5260: Postgre crashed unexpectedly

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Toni Helenius <toni(dot)helenius(at)syncrontech(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5260: Postgre crashed unexpectedly
Date: 2010-01-04 17:24:02
Message-ID: 603c8f071001040924qca01c92mef2d8759094d70dd@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Mon, Jan 4, 2010 at 5:29 AM, Toni Helenius
<toni(dot)helenius(at)syncrontech(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5260
> Logged by:          Toni Helenius
> Email address:      toni(dot)helenius(at)syncrontech(dot)com
> PostgreSQL version: 8.3.9
> Operating system:   Windows 2008 Server Enterprise
> Description:        Postgre crashed unexpectedly
> Details:
>
> Postgre database was running normally and several applications using it
> normally like any other day. Then the Postge just died and didn't recover by
> itself.. Here is the log:
[...]
> 2009-12-31 13:41:20 EET FATAL:  pre-existing shared memory block is still in
> use
> 2009-12-31 13:41:20 EET HINT:  Check if there are any old server processes
> still running, and terminate them.

Per the hint, did you check whether there are any old server processes
still running?

If you don't find any old server processes running, I would guess that
a reboot would likely be a good next step toward getting the system
back up.

Unfortunately I'm not sure what could have caused the original crash.

...Robert

In response to

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-01-04 17:55:24
Subject: Re: BUG #5259: the table name double
Previous:From: Robert HaasDate: 2010-01-04 17:21:29
Subject: Re: Failed to run initdb - not resolved bug 5130

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