BUG #6204: Using plperl functions generate crash

The following bug has been logged online:

Bug reference:      6204
Logged by:          pasman
Email address:      pasman.p@gmail.com
PostgreSQL version: 9.1.0
Operating system:   WinXP sp3
Description:        Using plperl functions generate crash
Details:

After install postgresql 9.1.0 and Activestate perl 5.14.1 execute:

create function perl_test() returns void as
$$
$$
language plperl


This generates server crash. Log contain:


2011-09-14 11:08:22 CEST STATEMENT:  create function perl_test() returns
void as     $$     $$     language plperl
2011-09-14 11:08:47 CEST LOG:  server process (PID 560) was terminated by
exception 0xC0000005
2011-09-14 11:08:47 CEST HINT:  See C include file "ntstatus.h" for a
description of the hexadecimal value.
2011-09-14 11:08:47 CEST LOG:  terminating any other active server
processes
2011-09-14 11:08:47 CEST WARNING:  terminating connection because of crash
of another server process
2011-09-14 11:08:47 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.
2011-09-14 11:08:47 CEST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2011-09-14 11:08:47 CEST WARNING:  terminating connection because of crash
of another server process
2011-09-14 11:08:47 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.
2011-09-14 11:08:47 CEST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2011-09-14 11:08:47 CEST WARNING:  terminating connection because of crash
of another server process
2011-09-14 11:08:47 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.
2011-09-14 11:08:47 CEST HINT:  In a moment you should be able to reconnect
to the database and repeat your command.
2011-09-14 11:08:47 CEST LOG:  all server processes terminated;
reinitializing
2011-09-14 11:08:57 CEST FATAL:  pre-existing shared memory block is still
in use
2011-09-14 11:08:57 CEST HINT:  Check if there are any old server processes
still running, and terminate them.