stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876

Hi everyone. The following error appeared in our log yesterday:

2009-11-19 13:39:40 PST:10.211.97.171(63815):[25668]: PANIC: stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876

Followed by:

2009-11-19 13:44:24 PST::@:[1381]: LOG: server process (PID 25668) was terminated by signal 6: Aborted
2009-11-19 13:44:24 PST::@:[1381]: LOG: terminating any other active server processes

Followed by:

2009-11-19 13:44:24 PST:10.211.1.171(8016):[29736]: WARNING: terminating connection because of crash of another server process
2009-11-19 13:44:24 PST:10.211.1.171(8016):[29736]: 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.
(repeated for every open connection).

Followed by:

2009-11-19 13:44:36 PST:[local]:postgres(at)postgres:[29780]: FATAL: the database system is in recovery mode
(repeated several times).

Finally:

2009-11-19 13:47:15 PST::@:[223331]: LOG: autovacuum launcher started
2009-11-19 13:47:15 PST::@:[1381]: LOG: database system is ready to accept connections

The system was under a good amount of load: approximately 80 connections, each generating large numbers of batched inserts (using JDBC). This includes the one that crashed. Once the database re-initialized, everything went back to normal. Is this due to a bug in PostgreSQL? Is there anything we can do about it? :-)

We are running PostgreSQL 8.3.8 (64-bit) on a dedicated Fedora Core 8 machine, in Amazon EC2. This was using an "extra-large" instance, which means 4 Xeon cores (2.66 GHz) and 15.5 GB of memory.

Sincerely,
Matt Solnit