Re: backtrace_on_internal_error

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: backtrace_on_internal_error
Date: 2023-12-08 23:36:01
Message-ID: 20231208233601.g2vcjyqm3n7kzzni@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-12-08 17:29:45 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-12-08 23:40:15 Re: backtrace_on_internal_error
Previous Message Tom Lane 2023-12-08 22:56:20 Re: micro-optimizing json.c