Fix check for conflicting SSL min/max protocol settings
Commit 79dfa8a has introduced a check to catch when the minimum protocol
version was set higher than the maximum version, however an error was
getting generated when both bounds are set even if they are able to
work, causing a backend to not use a new SSL context but keep the old
one.
Author: Daniel Gustafsson
Discussion: https://postgr.es/m/14BFD060-8C9D-43B4-897D-D5D9AA6FC92B@yesql.se
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/e30b0b5cfaeb4f1f739f82c34c5ae2773852a088
Modified Files
--------------
src/backend/libpq/be-secure-openssl.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)