| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Federico Di Gregorio <fog(at)initd(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: libpq not reentrant |
| Date: | 2002-01-18 17:23:17 |
| Message-ID: | 7819.1011374597@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> As of 7.2 we are only going to recommend crypt for backward
> compatibility with older releases. I will add a mention in libpq docs
> that crypt authentication is not thread-safe. Even when crypt did work
> it wasn't always portable between OS's. Is that how we want to go?
I really think that a mention in the docs (in the part where libpq
re-entrancy is discussed) is sufficient. Especially given how close
we are to 7.2 release. I would not favor adding a configure check
now, even if Federico had the patch ready to go...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Federico Di Gregorio | 2002-01-18 17:28:09 | Re: libpq not reentrant |
| Previous Message | Bruce Momjian | 2002-01-18 17:21:06 | Re: libpq not reentrant |