Re: Ensure that STDERR is empty during connect_ok - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Ensure that STDERR is empty during connect_ok
Date
Msg-id EB19BE4C-3CF7-463F-952E-953BDB44983E@yesql.se
Whole thread Raw
In response to Re: Ensure that STDERR is empty during connect_ok  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> On 6 Feb 2022, at 08:00, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Wed, Feb 02, 2022 at 03:40:39PM +0100, Daniel Gustafsson wrote:
>> As part of the NSS patchset, quite a few bugs (and NSS quirks) were found by
>> inspecting STDERR in connect_ok and require it to be empty.  This is not really
>> NSS specific, and could help find issues in other libraries as well so I
>> propose to apply it regardless of the fate of the NSS patchset.
>
> Sounds sensible from here.  Thanks!
>
> All the code paths seem to be covered, at quick glance.

Applied, minus the changes to the test plans which are no longer required after
549ec201d6.

--
Daniel Gustafsson        https://vmware.com/




pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints
Next
From: Christoph Heiss
Date:
Subject: Re: [PATCH] Add reloption for views to enable RLS