Re: PQinitSSL broken in some use casesf

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

On Sun, Mar 29, 2009 at 1:56 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I think this is where we got stuck because extending libpq with a new
> function is a larger API change, and not having a clear plan of what
> initialization stuff we might need in the future, it seems unwise, and
> also perhaps overkill.

right, maybe this is a case of 'the perfect being the enemy of the
good'...I have no qualms with fixing it now with the two argument
version. The stuff I'd like to see is a separate issue, I guess.

merlin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Kellerer 2009-03-30 12:06:27 Re: New shapshot RPMs (Mar 27, 2009) are ready for testing
Previous Message Kedar Potdar 2009-03-30 11:51:21 Re: Partitioning feature ...