Re: backtrace_on_internal_error - Mailing list pgsql-hackers

From Tom Lane
Subject Re: backtrace_on_internal_error
Date
Msg-id 1565611.1702082360@sss.pgh.pa.us
Whole thread Raw
In response to Re: backtrace_on_internal_error  (Andres Freund <andres@anarazel.de>)
Responses Re: backtrace_on_internal_error
Re: backtrace_on_internal_error
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2023-12-08 17:29:45 -0500, Tom Lane wrote:
>> 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?

Writes don't act that way, do they?  EOF on a pipe gives you an error,
not silently reporting that zero bytes were written and leaving you
to retry indefinitely.

What I was wondering about was if we needed similar changes on the
libpq side, but it's still about reads not writes.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: backtrace_on_internal_error
Next
From: Thomas Munro
Date:
Subject: Re: Streaming I/O, vectored I/O (WIP)