Re: PQinitSSL broken in some use casesf

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andrew Chernow <ac(at)esilo(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, 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-02-11 12:57:19
Message-ID: 75D6B238-BB91-4BDA-BA8B-43E813A6EE74@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Feb 11, 2009, at 12:12 AM, Andrew Chernow <ac(at)esilo(dot)com> wrote:

> Robert Haas wrote:
>> I am not in love with the idea of using PQinitSSL(SOME_MAGIC_VALUE)
>
> The issue I see is the inability to toggle crypto initialization.
> I think crypto init and ssl init are 2 different things. Thus, I
> proposed the below:
>
> http://archives.postgresql.org/pgsql-hackers/2009-02/msg00488.php

If that can be made transparent to existing apps, I'm all for it.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-02-11 13:05:20 Re: Optimization rules for semi and anti joins
Previous Message Peter Eisentraut 2009-02-11 11:59:29 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,