From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Refactor all TAP test suites doing connection checks
Date: Tue, 6 Apr 2021 09:11:02 +0900
Message-ID: <YGunFpb3U9zi5DV4@paquier.xyz> (raw)
In-Reply-To: <933130.1617665023@sss.pgh.pa.us>
References: <E1lTDox-0006rF-OV@gemulon.postgresql.org>
<513200.1617634642@sss.pgh.pa.us>
<YGuSe6Q484Eshj2n@paquier.xyz>
<932059.1617663467@sss.pgh.pa.us>
<933130.1617665023@sss.pgh.pa.us>
On Mon, Apr 05, 2021 at 07:23:43PM -0400, Tom Lane wrote:
> What does seem to fix it reliably is the attached.
Thanks for confirming. I am still surprised that this has not popped
up as an issue until now. Could that be because those animals have
never run the LDAP, SSL or kerberos test suites over the years? The
attached would address this issue, and I am going to apply it for the
buildfarm. LDAP and kerberos still use some queries, while the SSL
suite loses that, but as long as there is log_connections in the
configuration we'd still know about the connection attempts, so I
guess that's fine.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: michael@paquier.xyz, tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Refactor all TAP test suites doing connection checks
In-Reply-To: <YGunFpb3U9zi5DV4@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox