SQLSTATE 00000 and message level LOG get logged when a server process crashes

From: Vadim Kalinkin <vadim(dot)kalinkin(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: SQLSTATE 00000 and message level LOG get logged when a server process crashes
Date: 2014-07-16 07:14:08
Message-ID: CAM0b6+2yPMOfXc6FESOqGonj8tboyMvDx0SsgHDHoC=t4-Efwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello!

Say, some worker process was terminated for whatever reason.
In logfile that fact is reflected with messages by postmaster:

00000 2014-07-16 09:10:15.442 MSK [1755-5] d=,u=,h= LOG:
server process (PID 12652) was terminated by signal 11: Segmentation fault
00000 2014-07-16 09:10:15.442 MSK [1755-6] d=,u=,h= DETAIL:
Failed process was running: select * from <...>
00000 2014-07-16 09:10:15.442 MSK [1755-7] d=,u=,h= LOG:
terminating any other active server processes

(log_line_prefix = '%e %m [%p-%l] d=%d,u=%u,h=%h ')

Why SQLSTATE 00000 and message level LOG are used here?
Wouldn't SQLSTATE of Class 58 (System Error) and message level ERROR or
FATAL be more suitable here?

I'm asking because my log analyzer (pgBadger) completely missed that event.
Thanks.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marko Tiikkaja 2014-07-16 12:10:17 Re: BUG #10794: psql sometimes ignores .psqlrc
Previous Message Silambarasan Viswanathan 2014-07-16 06:29:39 Disable View rule