BUG #7597: exception 0xC0000005

The following bug has been logged on the website:

Bug reference: 7597
Logged by: Bo T Jensen
Email address: bo(at)budget123(dot)dk
PostgreSQL version: 9.1.6
Operating system: windows 7 home premium 64
Description:

Ive managed to boil this down to a repeatable example on a test setup, but
it was found originally on windows server 2008 (64 bit).

pg_log:
2012-10-11 11:29:49 CEST LOG: server process (PID 4400) was terminated by
exception 0xC0000005
2012-10-11 11:29:49 CEST HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
2012-10-11 11:29:49 CEST LOG: terminating any other active server
processes
2012-10-11 11:29:49 CEST WARNING: terminating connection because of crash
of another server process
2012-10-11 11:29:49 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.
2012-10-11 11:29:49 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2012-10-11 11:29:49 CEST WARNING: terminating connection because of crash
of another server process
2012-10-11 11:29:49 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.
2012-10-11 11:29:49 CEST HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2012-10-11 11:29:49 CEST LOG: all server processes terminated;
reinitializing
2012-10-11 11:29:59 CEST FATAL: pre-existing shared memory block is still
in use
2012-10-11 11:29:59 CEST HINT: Check if there are any old server processes
still running, and terminate them.

Offending sql looks like this:
select 1 from reference
where username = 'user1'
and (refid, '127.0.0.1', 'manager1') not in (select refid, ip, manager from
loguser);

Kind regards
Bo T Jensen