BUG #1917: autovaccuum crashes

The following bug has been logged online:

Bug reference:      1917
Logged by:          Theo Schlossnagle
Email address:      jesus@omniti.com
PostgreSQL version: 8.1devel
Operating system:   CentOS 4.1 (Linux 2.6.12.3)
Description:        autovaccuum crashes
Details:

We're running an otherwise idle instance.

Doing large data loads via the COPY command into a set of schema-identical
tables table1, table2, table3 all of which inherrit table. (simulating
Oracle's partitioning).  Periodically, we get:


LOG:  autovacuum process (PID 9685) was terminated by signal 11
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2005-09-27 09:12:49 PDT
...
LOG:  autovacuum process (PID 10116) was terminated by signal 11
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing
LOG:  database system was interrupted at 2005-09-27 10:39:19 PDT
...
LOG:  autovacuum process (PID 10626) was terminated by signal 11
LOG:  terminating any other active server processes
WARNING:  terminating connection because of crash of another server process
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.
HINT:  In a moment you should be able to reconnect to the database and
repeat your command.



The process doesn't seem to dump core.