Tom Lane wrote:
> "Dave Page" <[EMAIL PROTECTED]> writes:
>>> From: Tom Lane <[EMAIL PROTECTED]>
>>> ... It's not entirely clear whether BIO_new_fp() would avoid the
>>> problematic calls, but it doesn't look like it'd be hard to try.
>> The last version of the patch I posted uses BIO_new_file() in all cases, and 
>> (from memory) BIO_get_fp() in the non-win32 case to get a FILE* to pass to 
>> fstat.
> Did you manage to get rid of the bogus-error-message problem that
> afflicted the first version of the patch?  If so, this way is fine.

No, thats still an issue.

> If not, keeping control of file-opening in our own hands might be
> a way to dodge that.

That doesn't work because we still end up passing FILE pointers between
potentially differing runtime builds/versions) which OpenSSL then
detects and bleats about including OPENSSL_Applink().


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to