From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Chernow <ac(at)esilo(dot)com>, Merlin Moncure <mmoncure(at)gmail(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 17:52:29 |
Message-ID: | 200903301752.n2UHqTx02864@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > Bruce Momjian wrote:
> >> Are we sure we don't want to add a more general libpq initialization
> >> control at this time?
> >>
> >> PQinitOptions(PG_NO_SSL_INIT | PG_NO_CRYPTO_INIT);
>
> > Could be an option but if we go down that path, it needs to be
> > PG_NO_OPENSSL_SSL_INIT and PG_NO_OPENSSL_CRYPTO_INIT....
>
> And we get into the whole question of error handling, which is what
> shot down that proposal last time.
Can you remind me of the details? I don't remember that issue.
Currently PQinitSSL() returns void, so I don't see an issue there.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-03-30 18:04:00 | Re: More message encoding woes |
Previous Message | Heikki Linnakangas | 2009-03-30 17:47:58 | Re: More message encoding woes |