aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/xml.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2019-03-19 16:58:20 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2019-03-19 16:58:20 -0400
commit08cf04bb4747269dde46b45346b7f38653013002 (patch)
treee62ebad4c1379e659561d2b93b26fb675f34498c /src/backend/utils/adt/xml.c
parentcba8fc68823e1915b35182e87f507e46b5ac7b67 (diff)
downloadpostgresql-08cf04bb4747269dde46b45346b7f38653013002.tar.gz
postgresql-08cf04bb4747269dde46b45346b7f38653013002.zip
Hack back-branch SSL tests to avoid intermittent buildfarm failures.
Buildfarm member eelpout sometimes reports the wrong error message for an SSL connection failure. In HEAD, this problem is believed to be solved by commit 1f39a1c06, but I'm as yet unwilling to back-patch that. The problem seems fairly unlikely to be an issue in the field, since (as far as we can tell) it happens only during a failure of a local-loopback SSL connection, and it's improbable even then. It seems better to just live with it for the time being; but let's tweak the regression test to accept the other error message as a "pass". Needed in v11 only, since older branches didn't check the message text anyway. Discussion: https://postgr.es/m/CAEepm=2n6Nv+5tFfe8YnkUm1fXgvxR0Mm1FoD+QKG-vLNGLyKg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions