| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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 19:51:15 |
| Message-ID: | 3569.1238269875@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Well, we are not the "Make Merlin Happy club". ;-)
Merlin and Andrew were the ones complaining initially. If they feel
that a proposed patch doesn't fix the problem, then I'd say that it
isn't fixing the problem.
> My personal opinion is that adding #defines to PQinitSSL() is the right
> level of fix, and if we ever implement a libpq init mechanism we can
> convert PGinitSSL to a macro. I am attaching a sample patch for
> feedback.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Chernow | 2009-03-28 20:22:01 | Re: PQinitSSL broken in some use casesf |
| Previous Message | Bruce Momjian | 2009-03-28 19:31:17 | Re: Should SET ROLE inherit config params? |