Skip site navigation (1) Skip section navigation (2)

Re: libpq not reentrant

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 (view raw or flat)
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

In response to

Responses

pgsql-bugs by date

Next:From: Federico Di GregorioDate: 2002-01-18 17:28:09
Subject: Re: libpq not reentrant
Previous:From: Bruce MomjianDate: 2002-01-18 17:21:06
Subject: Re: libpq not reentrant

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group