| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Asif Naeem <anaeem(dot)it(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Thom Brown <thom(at)linux(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.5: Can't connect with PGSSLMODE=require on Windows |
| Date: | 2015-09-28 21:45:18 |
| Message-ID: | 9454.1443476718@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> We now probably could remove
> * XXX OpenSSL 1.0.1e considers many more errcodes than just EINTR as reasons
> * to retry; do we need to adopt their logic for that?
> since we now actually check for more tahn just EINTR.
Well, that comment is cloned from the backend which is already checking
for all three of these errno codes. I am too lazy to go look at the
OpenSSL code right now, but my recollection is that they checked for
some truly weird stuff, not just the expected spellings of EINTR.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-09-28 21:47:26 | Re: Rework the way multixact truncations work |
| Previous Message | Andres Freund | 2015-09-28 21:34:21 | Re: 9.5: Can't connect with PGSSLMODE=require on Windows |