From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Chernow <ac(at)esilo(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 19:15:39 |
Message-ID: | 603c8f070903301215v7dcb057fk60467886c60d1e8f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 30, 2009 at 2:59 PM, Andrew Chernow <ac(at)esilo(dot)com> wrote:
> 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.
I guess that'd work but it might be overkill.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-30 19:27:45 | Re: PQinitSSL broken in some use casesf |
Previous Message | Andrew Chernow | 2009-03-30 18:59:08 | Re: PQinitSSL broken in some use casesf |