Magnus Hagander wrote:
> On 30 mar 2009, at 17.24, Andrew Chernow <ac(at)esilo(dot)com> wrote:
> > Tom Lane wrote:
> >> BTW, unless someone objects I'd like to make the name of that
> >> function
> >> PQinitSecurity.
> > Agreed. Although, both PQinitSecure and PQinitSecurity are very
> > general names. "Security" can mean a lot of things. Maybe the name
> > should be more particular, like PQinitOpenSSL. I think its okay to
> > reference the openssl project name being how this function is
> > designed to work with openssl's library split.
> It's quite likely that well want to support another ssl library in the
> future. At least likely enough that any api we define should take it
> into consideration.
Are we sure we don't want to add a more general libpq initialization
control at this time?
PQinitOptions(PG_NO_SSL_INIT | PG_NO_CRYPTO_INIT);
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
+ If your life is a hard drive, Christ can be your backup. +
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2009-03-30 17:44:13|
|Subject: Re: PQinitSSL broken in some use casesf|
|Previous:||From: Tom Lane||Date: 2009-03-30 17:31:23|
|Subject: Re: Unexpected Result in Windowing |