Postgres Pro
Downloads
Home   >   mailing lists

Re: SIGABRT causes messages at LOG but not PANIC - Mailing list pgsql-hackers

From Tom Lane
Subject Re: SIGABRT causes messages at LOG but not PANIC
Date
Msg-id 1471008.1636575613@sss.pgh.pa.us
Whole thread Raw
In response to SIGABRT causes messages at LOG but not PANIC  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
Tree view 
Justin Pryzby <pryzby@telsasoft.com> writes:
> I'm surprised that not a single message was logged at PANIC, even though it's
> defined to mean:

The backend you killed didn't get a chance to log anything.

Or to put it another way: a PANIC ereport is the trigger for a database
restart, not a response to some other event that has triggered one.

            regards, tom lane

pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display
Next
From: Tom Lane
Date:
Subject: Re: [EXTERNAL] Re: PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings