Ensure that STDERR is empty during connect_ok

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Jacob Champion <pchampion(at)vmware(dot)com>
Subject: Ensure that STDERR is empty during connect_ok
Date: 2022-02-02 14:40:39
Message-ID: 9D4FFB61-392B-4A2C-B7E4-911797B4AC14@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

(The change in the SCRAM tests stems from this now making all testruns have the
same number of tests. While I prefer to not plan at all and instead run
done_testing(), doing that consistently is for another patch, keeping this with
the remainder of the suites.)

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

Attachment Content-Type Size
0001-Ensure-that-STDERR-is-empty-in-connect_ok-tests.patch application/octet-stream 4.5 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-02-02 14:46:35 Re: Add checkpoint and redo LSN to LogCheckpointEnd log message
Previous Message Julien Rouhaud 2022-02-02 14:16:30 Re: Deparsing rewritten query