From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | pgman(at)candle(dot)pha(dot)pa(dot)us |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kris Jurka <books(at)ejurka(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Don't try to compile SSL CRL support |
Date: | 2006-05-05 19:01:52 |
Message-ID: | 200605051901.k45J1qq12020@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
pgman wrote:
> Tom Lane wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > The attached patch checks for the file, and either user it or generates
> > > a log message that it was skipped.
> >
> > I still can't get excited about this. Who will it help? The DBA who is
> > silly enough to think his ancient SSL library supports CRL is probably
> > also silly enough not to read the postmaster log carefully. It would
> > make a whole lot more sense just to document that OpenSSL < whatever
> > doesn't support CRL.
>
> Why hard-code something if we can dynamically report it, and NetBSD 2.0
> isn't that old.
Sorry, I meant NetBSD 1.6/canary:
http://www.pgbuildfarm.org/cgi-bin/show_history.pl?nm=canary&br=HEAD
Anyway, if we are doing CRL, we should do it right.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-05 19:13:04 | Re: Page at a time index scan |
Previous Message | Joshua D. Drake | 2006-05-05 18:56:44 | Re: plpython improvements |