@ 2006-01-02 15:02:02 MST:LOG:  autovacuum: processing database "tigris"
@ 2006-01-02 15:03:01 MST:LOG:  server process (PID 28772) was terminated by signal 11
@ 2006-01-02 15:03:01 MST:LOG:  terminating any other active server processes
[local]@[local] 2006-01-02 15:03:01 MST:WARNING:  terminating connection because of crash of another server process
[local]@[local] 2006-01-02 15:03:01 MST: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.
[local]@[local] 2006-01-02 15:03:01 MST:HINT:  In a moment you should be able to reconnect to the database and repeat your command.
192.168.19.129(50732)@192.168.19.129 2006-01-02 15:03:01 MST:WARNING:  terminating connection because of crash of another server process
192.168.19.129(50732)@192.168.19.129 2006-01-02 15:03:01 MST: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.
192.168.19.129(50732)@192.168.19.129 2006-01-02 15:03:01 MST:HINT:  In a moment you should be able to reconnect to the database and repeat your command.
192.168.19.129(50730)@192.168.19.129 2006-01-02 15:03:01 MST:WARNING:  terminating connection because of crash of another server process
192.168.19.129(50730)@192.168.19.129 2006-01-02 15:03:01 MST: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.
192.168.19.129(50730)@192.168.19.129 2006-01-02 15:03:01 MST:HINT:  In a moment you should be able to reconnect to the database and repeat your command.
192.168.19.129(50731)@192.168.19.129 2006-01-02 15:03:01 MST:WARNING:  terminating connection because of crash of another server process
192.168.19.129(50731)@192.168.19.129 2006-01-02 15:03:01 MST: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.
192.168.19.129(50731)@192.168.19.129 2006-01-02 15:03:01 MST:HINT:  In a moment you should be able to reconnect to the database and repeat your command.
@ 2006-01-02 15:03:01 MST:LOG:  all server processes terminated; reinitializing
@ 2006-01-02 15:03:01 MST:LOG:  database system was interrupted at 2006-01-02 15:02:47 MST
@ 2006-01-02 15:03:01 MST:LOG:  checkpoint record is at 37/D60F93A8
@ 2006-01-02 15:03:01 MST:LOG:  redo record is at 37/D6008018; undo record is at 0/0; shutdown FALSE
@ 2006-01-02 15:03:01 MST:LOG:  next transaction ID: 32196280; next OID: 102041945
@ 2006-01-02 15:03:01 MST:LOG:  next MultiXactId: 41; next MultiXactOffset: 93
@ 2006-01-02 15:03:01 MST:LOG:  database system was not properly shut down; automatic recovery in progress
@ 2006-01-02 15:03:01 MST:LOG:  redo starts at 37/D6008018
@ 2006-01-02 15:03:01 MST:LOG:  record with zero length at 37/D60F93F8
@ 2006-01-02 15:03:01 MST:LOG:  redo done at 37/D60F93A8
@ 2006-01-02 15:03:02 MST:LOG:  database system is ready
@ 2006-01-02 15:03:02 MST:LOG:  transaction ID wrap limit is 1087118600, limited by database "cert"