| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Hubert Zhang <zhubert(at)vmware(dot)com>, tsunakawa(dot)takay(at)fujitsu(dot)com, pgsql-hackers(at)postgresql(dot)org, Andreas Seltenreich <seltenreich(at)gmx(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: Multiple hosts in connection string failed to failover in non-hot standby mode |
| Date: | 2021-06-01 07:34:44 |
| Message-ID: | YLXjFOV3teAPirmS@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 31, 2021 at 09:07:38PM -0400, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>>> Agreed, that seems bogus.
>
>> There may be others, and I have not checked yet. I'd rather do a
>> backpatch for this part, would you agree?
>
> +1
Playing with all those variables and broken values here and there, I
have been able to break a bunch of tests. Most of the failures were
in the authentication and SSL tests, but there were also fancier
cases. For example, PGCLIENTENCODING would cause a failure with
pg_ctl, for any TAP test.
I got surprised that enforcing values for most of the PGSSL* ones did
not cause a failure when it came to the certs, CRLs keys and root
certs now. Still, I think that we'd be safer to cancel these as
well.
Attached is the list I am finishing with. I'd like to fix that, so
please let me know if there are any comments or objections.
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| testlib-envs.patch | text/x-diff | 1006 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2021-06-01 07:43:44 | Re: Alias collision in `refresh materialized view concurrently` |
| Previous Message | Peter Smith | 2021-06-01 07:32:33 | Re: locking [user] catalog tables vs 2pc vs logical rep |