Re: Ensure that STDERR is empty during connect_ok

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
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-06 07:00:58
Message-ID: Yf9yKiRnvFdW8blk@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-02-06 07:03:11 Re: pg_upgrade should truncate/remove its logs before running
Previous Message Tom Lane 2022-02-06 06:58:21 Re: pg_upgrade should truncate/remove its logs before running