aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/arrayfuncs.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-04-03 20:49:08 +0900
committerMichael Paquier <michael@paquier.xyz>2021-04-03 20:49:08 +0900
commit8d3a4c3eae5367fba60ab77c159814defba784fe (patch)
treef9014760908f5b3aea7830e96379acee4dd681e6 /src/backend/utils/adt/arrayfuncs.c
parente6bdfd9700ebfc7df811c97c2fc46d7e94e329a2 (diff)
downloadpostgresql-8d3a4c3eae5367fba60ab77c159814defba784fe.tar.gz
postgresql-8d3a4c3eae5367fba60ab77c159814defba784fe.zip
Use more verbose matching patterns for errors in SSL TAP tests
The TAP tests of src/test/ssl/ have been using rather generic matching patterns to check some failure scenarios, like "SSL error" or just "FATAL". These have been introduced in 081bfc1. Those messages are not wrong per se, but when working on the integration of new SSL libraries it becomes hard to know if those errors are legit or not, and existing scenarios may fail in incorrect ways. This commit makes all those messages more verbose by adding the information generated by OpenSSL. Fortunately, the same error messages are used for all the versions supported on HEAD (checked that after running the tests from 1.0.1 to 1.1.1), so the change is straight-forward. Reported-by: Jacob Champion, Álvaro Herrera Discussion: https://postgr.es/m/YGU3AxQh0zBMMW8m@paquier.xyz
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions