Magnus Hagander wrote:
Yes, that was the problem. Attached patch fixes the problem for me on
Windows and Linux using the error mark functionality. It seems a lot
cleaner than the other option.
>
Dave - can you test this one? Assuming that works, I'll go ahead and apply
it.
Yep, looks good here. Thanks.
I also think we have the same problem in the current code, just not for
fopen(). We trap fopen() without anything happening inside OpenSSL, but if
we get an error in the OpenSSL functions we call, something similar would
likely happen.
Should we backpatch all the stuff, or just the error push/pop thing?
All of it. Anyone building just libpq/psql using the old MSVC makefiles
will probably see the applink problem if they try to use client certs.
/D
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
