Re: Ensure that STDERR is empty during connect_ok

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jacob Champion <pchampion(at)vmware(dot)com>
Subject: Re: Ensure that STDERR is empty during connect_ok
Date: 2022-02-15 11:52:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 6 Feb 2022, at 08:00, Michael Paquier <michael(at)paquier(dot)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

Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Heiss 2022-02-15 12:02:29 Re: [PATCH] Add reloption for views to enable RLS
Previous Message Dilip Kumar 2022-02-15 11:48:47 Re: [Proposal] Fully WAL logged CREATE DATABASE - No Checkpoints