Re: PQinitSSL broken in some use casesf

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Chernow <ac(at)esilo(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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-03-28 20:26:48
Message-ID: 200903282026.n2SKQms09429@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Chernow wrote:
> Tom Lane wrote:
> > This is just a rehash of one of the patches that was discussed earlier.
> > There wasn't consensus for it then, and there's not now.
> >
>
> I am personally out of ideas. It feels like this issue has been beaten
> to death. There are only a few ways to do it and I believe they have
> all been put on the table. Any suggestions?

Well, at least the current behavior is documented now. I personally
thought the #define was the best minimal fix because it only added a few
lines to the docs and the C code.

--
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. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2009-03-28 20:52:02 Re: PQinitSSL broken in some use casesf
Previous Message Bruce Momjian 2009-03-28 20:25:15 Re: psql \d* and system objects