Re: PQinitSSL broken in some use casesf

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQinitSSL broken in some use casesf
Date: 2009-03-30 18:59:08
Message-ID: 49D1167C.9050405@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> Or we might need a whole "char *" or "int" argument for some purpose
> unrelated to SSL. Then we'll have a PQinit() function that pretends
> to be a general-purpose initialization mechanism but really isn't.
>

I proposed a PQinit() that included a void data pointer argument. The
idea was PQinit(which, data, data_len) would be called multiple times to
init different things.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-03-30 19:15:39 Re: PQinitSSL broken in some use casesf
Previous Message Andrew Chernow 2009-03-30 18:56:04 Re: PQinitSSL broken in some use casesf