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

BUG #5628: 9.0beta4 failed automatic crash recovery

From: "Itagaki Takahiro" <itagaki(dot)takahiro(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5628: 9.0beta4 failed automatic crash recovery
Date: 2010-08-24 00:28:14
Message-ID: 201008240028.o7O0SEcw018701@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5628
Logged by:          Itagaki Takahiro
Email address:      itagaki(dot)takahiro(at)gmail(dot)com
PostgreSQL version: 9.0b4 (32bit)
Operating system:   Windows 7 (64bit)
Description:        9.0beta4 failed automatic crash recovery
Details: 

9.0beta4 seems to fail automatic crash recovery after
some of backend processes crashed, though 8.2 succeeded
to recover. This is a rare error case, but some logic
for shared memory might be broken between versions.

I crashed a backend as a test manually with "pg_ctl kill":
  pg_ctl kill QUIT <backend-pid>

9.0 server has gone with the following logs:
----
WARNING:  terminating connection because of crash of another server process
...
LOG:  all server processes terminated; reinitializing
FATAL:  pre-existing shared memory block is still in use
HINT:  Check if there are any old server processes still running, and
terminate them.
----

But 8.2 can recover as expected:
----
WARNING:  terminating connection because of crash of another server process
...
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at <timestamp>
----

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-08-24 00:45:33
Subject: Re: BUG #5628: 9.0beta4 failed automatic crash recovery
Previous:From: Robert HaasDate: 2010-08-23 18:32:47
Subject: Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session

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