BUG #4962: Pre-existing shared memory block is still in use

From: "Carlos Alonso" <calonso(at)ictel(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4962: Pre-existing shared memory block is still in use
Date: 2009-08-04 10:49:52
Message-ID: 200908041049.n74AnqjX000754@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 4962
Logged by: Carlos Alonso
Email address: calonso(at)ictel(dot)com
PostgreSQL version: 8.3.6
Operating system: Windows XP Home Edition Version 2002 Service Pack 3
Description: Pre-existing shared memory block is still in use
Details:

2009-08-01 15:36:08 CEST LOG: server process (PID 5892) was terminated by
exception 0xC0000142
2009-08-01 15:36:08 CEST HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
2009-08-01 15:36:08 CEST LOG: terminating any other active server
processes
2009-08-01 15:36:08 CEST WARNING: terminating connection because of crash
of another server process
2009-08-01 15:36:08 CEST DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2009-08-01 15:36:08 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-08-01 15:36:08 CEST WARNING: terminating connection because of crash
of another server process
2009-08-01 15:36:08 CEST DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2009-08-01 15:36:08 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
[...]
2009-08-01 15:36:08 CEST WARNING: terminating connection because of crash
of another server process
2009-08-01 15:36:08 CEST DETAIL: The postmaster has commanded this server
process to roll back the current transaction and exit, because another
server process exited abnormally and possibly corrupted shared memory.
2009-08-01 15:36:08 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-08-01 15:36:08 CEST FATAL: the database system is in recovery mode
2009-08-01 15:36:08 CEST FATAL: the database system is in recovery mode
2009-08-01 15:36:08 CEST LOG: all server processes terminated;
reinitializing
2009-08-01 15:36:09 CEST FATAL: pre-existing shared memory block is still
in use
2009-08-01 15:36:09 CEST HINT: Check if there are any old server processes
still running, and terminate them.

There was no old server processes running.
This has happened twice in two weeks, the system was working for five
months.

It is enough rebooting the computer in one case, and starting the postgres
service by windows's services.msc in the other.

Thank's.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message William Crawford 2009-08-04 13:11:51 BUG #4963: Selecting timestamp without timezone at timezone gives wrong output
Previous Message Pavel Stehule 2009-08-04 09:30:40 Fwd: [BUGS] fix: plpgsql: return query and dropped columns problem