Re: PQinitSSL broken in some use casesf - Mailing list pgsql-hackers

From Andrew Chernow
Subject Re: PQinitSSL broken in some use casesf
Date
Msg-id 4995C9F3.1050905@esilo.com
Whole thread Raw
In response to Re: PQinitSSL broken in some use casesf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PQinitSSL broken in some use casesf
Re: PQinitSSL broken in some use casesf
List pgsql-hackers
> At this point I like Merlin's proposal of a third parameter value to
> PQinitSSL the best.

I'm not opposed to it, although I don't think it is as clean as a new 
function.

> 
> Also, this definition feels a bit wrong --- it's not possible for
> all four cases to be valid, is it?
> 

Yes it is.

PQinitSSLExtended(0, 0); // don't init anything, PQinitSSL(0)
PQinitSSLExtended(1, 0); // init ssl, don't init crypto
PQinitSSLExtended(0, 1); // don't init ssl, init crypto
PQinitSSLExtended(1, 1); // init both, default behavior, PQinitSSL(1)

-- 
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: PQinitSSL broken in some use casesf
Next
From: Andrew Chernow
Date:
Subject: Re: PQinitSSL broken in some use casesf