From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | shridhar_daithankar(at)persistent(dot)co(dot)in |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: |
Date: | 2003-07-24 12:59:38 |
Message-ID: | 200307241259.h6OCxcP14638@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Shridhar Daithankar wrote:
> On 23 Jul 2003 at 13:35, Bruce Momjian wrote:
> > I thought glibc was the one to introduce libc_r in the first place ---
> > are they making libc thread-safe now?
>
> AFAIK, glibc plays all threadsafe in glibc2. Don't know prior to that. Of
> course they do record if some of the routines are not thread safe but there is
> no separate library as such.
>
> by now, it is over all threadsafe. I don't have list of exceptions, but surely
> they are pretty small, if any.
>
> >
> > What OS's are still using libc_r for threaded-ness? I never liked that
> > approach myself, and I resist adding it to our setup unless it is
> > required.
>
> FreeBSD and windows..:-) Two I know of..
The strange thing is that accoring to template/freebsd, libc_r was
_added_ in FreeBSD 5.0, while most OS are moving away from separate
threaded libs.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Larry Rosenman | 2003-07-24 13:09:52 | Re: libpq_r |
Previous Message | Bruce Momjian | 2003-07-24 12:52:37 | Re: libpq_r |