SQLSTATE 00000 and message level LOG get logged when a server process crashes - Mailing list pgsql-bugs

From Vadim Kalinkin
Subject SQLSTATE 00000 and message level LOG get logged when a server process crashes
Date
Msg-id CAM0b6+2yPMOfXc6FESOqGonj8tboyMvDx0SsgHDHoC=t4-Efwg@mail.gmail.com
Whole thread Raw
Responses Re: SQLSTATE 00000 and message level LOG get logged when a server process crashes  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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.

pgsql-bugs by date:

Previous
From: Pavan Deolasee
Date:
Subject: Re: BUG #10675: alter database set tablespace and unlogged table
Next
From: Marko Tiikkaja
Date:
Subject: Re: BUG #10794: psql sometimes ignores .psqlrc