Re: Better client reporting for "immediate stop" shutdowns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Better client reporting for "immediate stop" shutdowns
Date: 2020-12-29 23:05:20
Message-ID: 2240761.1609283120@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> I had a thought while looking at elog.c: we could further reduce the risk
> of quickdie() crashing if we make it do what elog.c does when it gets into
> error recursion trouble:
> error_context_stack = NULL;
> debug_query_string = NULL;

On closer inspection, there's not much need to touch debug_query_string
here, because elog.c only consults that for making log entries, which
we're suppressing. I pushed it with just the error_context_stack reset.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2020-12-29 23:08:05 Re: create table like: ACCESS METHOD
Previous Message Tom Lane 2020-12-29 22:06:20 Re: Cleanup some -I$(libpq_srcdir) in makefiles