Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Paquier
Subject Re: Ensure that STDERR is empty during connect_ok
Date
Msg-id Yf9yKiRnvFdW8blk@paquier.xyz
Whole thread Raw
In response to Ensure that STDERR is empty during connect_ok  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Ensure that STDERR is empty during connect_ok  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade should truncate/remove its logs before running
Next
From: Tom Lane
Date:
Subject: Re: pg_upgrade should truncate/remove its logs before running