BUG #5669: server process was terminated by exception 0xC0000005 - Mailing list pgsql-bugs

The following bug has been logged online:

Bug reference:      5669
Logged by:          Andrew Geery
Email address:      andrew.geery@gmail.com
PostgreSQL version: 9.0
Operating system:   Windows Vista
Description:        server process was terminated by exception 0xC0000005
Details:

My PG 9.0 DB (EnterpriseDB edition 32-bit) on Windows Vista SP1 crashes
pretty predictably.

I executed some SQL and the server crashes.

Actually, the SQL completes successfully and then the server crashes.

I've tried rebooting my workstation which is running the db server but that
doesn't fix things.  Searching through the mail archives, the usual advice
is to disable virus protection and firewalls.

Let me know what other information I can supply!

Thanks
Andrew

2010-09-21 14:23:03 EDT LOG:  connection authorized: user=postgres
database=beast
2010-09-21 14:23:04 EDT LOG:  connection received: host=127.0.0.1
port=50101
2010-09-21 14:23:04 EDT LOG:  connection authorized: user=postgres
database=beast
2010-09-21 14:23:05 EDT LOG:  disconnection: session time: 0:00:01.412
user=postgres database=beast host=127.0.0.1 port=50101
2010-09-21 14:23:05 EDT LOG:  disconnection: session time: 0:00:02.640
user=postgres database=beast host=127.0.0.1 port=50100
2010-09-21 14:24:08 EDT LOG:  server process (PID 1004) was terminated by
exception 0xC0000005
2010-09-21 14:24:08 EDT HINT:  See C include file "ntstatus.h" for a
description of the hexadecimal value.
2010-09-21 14:24:08 EDT LOG:  terminating any other active server processes
2010-09-21 14:24:08 EDT WARNING:  terminating connection because of crash of
another server process
2010-09-21 14:24:08 EDT 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.
2010-09-21 14:24:08 EDT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2010-09-21 14:24:08 EDT WARNING:  terminating connection because of crash of
another server process
2010-09-21 14:24:08 EDT 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.
2010-09-21 14:24:08 EDT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2010-09-21 14:24:08 EDT WARNING:  terminating connection because of crash of
another server process
2010-09-21 14:24:08 EDT 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.
2010-09-21 14:24:08 EDT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2010-09-21 14:24:08 EDT WARNING:  terminating connection because of crash of
another server process
2010-09-21 14:24:08 EDT 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.
2010-09-21 14:24:08 EDT HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2010-09-21 14:24:08 EDT LOG:  all server processes terminated;
reinitializing
2010-09-21 14:24:18 EDT FATAL:  pre-existing shared memory block is still in
use
2010-09-21 14:24:18 EDT HINT:  Check if there are any old server processes
still running, and terminate them.