Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Andres Freund
Subject Re: backtrace_on_internal_error
Date
Msg-id 20231208233601.g2vcjyqm3n7kzzni@awork3.anarazel.de
Whole thread Raw
In response to Re: backtrace_on_internal_error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: backtrace_on_internal_error
List pgsql-hackers
On 2023-12-08 17:29:45 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> >> I think I figured it it out. Looks like we need to translate a closed socket
> >> (recvfrom() returning 0) to ECONNRESET or such.
> 
> > Seems like we should just treat errno == 0 as a reason to emit the "EOF
> > detected" message?
> 
> Agreed.  I think we want to do that after the initial handshake,
> too, so maybe as attached.

I was wondering about that too. But if we do so, why not also do it for
writes?



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: micro-optimizing json.c
Next
From: Andres Freund
Date:
Subject: Re: backtrace_on_internal_error