| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rare SSL failures on eelpout |
| Date: | 2019-03-19 00:54:40 |
| Message-ID: | 12018.1552956880@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Yeah, now that we understand this properly I agree this is unlikely to
> bother anyone in real life. I just want to make the build farm green.
> I wondered about ssl_max_protocol_version = 'TLSv1.2', but that GUC's
> too new.
Yeah; also, forcing that would reduce our test coverage.
> Another option would be to change the "command_fails_like"
> pattern to tolerate both errors in v11.
This might be a reasonable stopgap measure, since it'd basically
only affect buildfarm results.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Imai, Yoshikazu | 2019-03-19 01:18:55 | RE: speeding up planning with partitions |
| Previous Message | Masahiko Sawada | 2019-03-19 00:31:47 | Re: [HACKERS] Block level parallel vacuum |