2012-05-08 20:03:16 UTC WARNING:  worker took too long to start; canceled
2012-05-08 20:03:59 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:03:59 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:04:08 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:04:10 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:04:13 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:04:15 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:04:16 UTC WARNING:  worker took too long to start; canceled
2012-05-08 20:05:41 UTC LOG:  server process (PID 3955) was terminated by signal 6: Aborted
2012-05-08 20:05:41 UTC LOG:  terminating any other active server processes
2012-05-08 20:05:41 UTC WARNING:  terminating connection because of crash of another server process
2012-05-08 20:05:41 UTC 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-05-08 20:05:41 UTC HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2012-05-08 20:04:16 UTC PANIC:  stuck spinlock (0x7fef6b799d80) detected at proc.c:269
2012-05-08 20:05:41 UTC WARNING:  terminating connection because of crash of another server process
2012-05-08 20:05:41 UTC 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-05-08 20:05:41 UTC HINT:  In a moment you should be able to reconnect to the database and repeat your command.