Re: SIGABRT causes messages at LOG but not PANIC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SIGABRT causes messages at LOG but not PANIC
Date: 2021-11-10 20:20:13
Message-ID: 1471008.1636575613@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Justin Pryzby <pryzby(at)telsasoft(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-11-10 21:06:46 Re: [EXTERNAL] Re: PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings
Previous Message Euler Taveira 2021-11-10 20:09:43 Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display