The only FATAL message when the error occurred was this 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. FATAL: the database system is in recovery mode 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. We do have java code called by pl/java ...but there seems to be no indication on why the crash occurred. On 10/20/09, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Anj Adu <fotographs@xxxxxxxxx> writes: >> I ocassionally get this error when a large insert is made to a very >> large table (Postgres 8.1.9) > >> LOG: server process (PID 25002) exited with exit code 1 > > The interesting messages would be before that one, I think. This > should indicate a FATAL exit, and that should have gotten logged. > > Another possibility is that you've got some non-postgres code loaded > into the backend that is doing exit(1). > > regards, tom lane > -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
