Skip site navigation (1) Skip section navigation (2)

Re: OpenSSL Applink

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: OpenSSL Applink
Date: 2007-09-28 16:55:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Dave Page <dpage(at)postgresql(dot)org> writes:
> Tom Lane wrote:
>> Doesn't really matter.  Even if we were willing to hack our own client
>> apps like that (which I'm not), we can *not* transfer such a requirement
>> onto every libpq-using application.  It's just not acceptable.

> *We're* not transfering any requirement. I've fixed pgAdmin for example 
> without any need to touch any Postgres code.

Well, yeah, we are, as evidenced by the fact that you had to do
something to pgAdmin.  Every other application that uses libpq would
also be facing source code changes to make it work.

Is there really no way to solve this within libpq?

			regards, tom lane

In response to


pgsql-patches by date

Next:From: Dave PageDate: 2007-09-28 18:24:01
Subject: Re: OpenSSL Applink
Previous:From: Andrew DunstanDate: 2007-09-28 16:40:25
Subject: Re: OpenSSL Applink

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group