| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Refactor all TAP test suites doing connection checks |
| Date: | 2021-04-06 00:15:31 |
| Message-ID: | 935457.1617668131@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> 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?
Dunno. Certainly most animals that enable TAP at all should be
running the "authentication" test, but those others all need to
be manually enabled, I believe. My own animals run the SSL test
but not LDAP or kerberos.
I'm fairly sure that we've previously fixed this exact same issue
in some tests that expected a connection failure ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-04-06 00:19:52 | pgsql: Allocate access strategy in parallel VACUUM workers. |
| Previous Message | Michael Paquier | 2021-04-06 00:11:02 | Re: pgsql: Refactor all TAP test suites doing connection checks |