Re: backtrace_on_internal_error
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-12-08T23:40:15Z
Lists: pgsql-hackers
Hi, On 2023-12-08 17:35:26 -0500, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > I thought it'd be nice to have a test for this, particularly because it's not > > clear that the behaviour is consistent across openssl versions. > > Perhaps, but ... > > > To deal with that, I changed the test to instead check if "not accept SSL > > connection: Success" is not logged. > > ... testing only that much seems entirely not worth the cycles, given the > shape of the patches we both just made. If we can't rely on "errno != 0" > to ensure we won't get "Success", there is one heck of a lot of other > code that will be broken worse than this. I was certainly more optimistic about the usefullness of the test before disocvering the above difficulties... I considered accepting both ECONNRESET and the errno = 0 phrasing, but after discovering that the phrasing differs between platforms that seemed less attractive. I guess the test might still provide some value, by ensuring those paths are reached. Greetings, Andres Freund
Commits
-
Add GUC backtrace_on_internal_error
- a740b213d4b4 17.0 landed
-
Fix variable name and comment
- 541e8f14a185 17.0 landed
-
Be more wary about OpenSSL not setting errno on error.
- ebbd499d4b55 16.2 landed
- 87b46ad90491 13.14 landed
- 551d4b28e445 15.6 landed
- 271d24f31ddd 12.18 landed
- 0a5c46a7a488 17.0 landed
- 07ce2432682d 14.11 landed