Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)
От | Marc G. Fournier |
---|---|
Тема | Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...) |
Дата | |
Msg-id | 20030901142339.I76431@ganymede.hub.org обсуждение исходный текст |
Ответ на | Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...) (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)
|
Список | pgsql-hackers |
On Mon, 1 Sep 2003, Bruce Momjian wrote: > Larry Rosenman wrote: > > > > > > --On Monday, September 01, 2003 12:35:43 -0400 Bruce Momjian > > <pgman@candle.pha.pa.us> wrote: > > > > > > > >> Um. I don't think that's true. I mean, in theory it's true, but in > > >> practice why would an OS have some *_r but have only non-thread-safe > > >> versions of others? > > > > > > Oh, interesting. So you are saying that if the OS supports threads, > > > then we use the *_r if they have them, and assume the non *_r functions > > > are already thread-safe if they don't. Interesting. > > > > > > That seems to be what we have on Unixware, and on BSD/OS I have some *_r > > > functions but not others, but they are all threadsafe, so your plan > > > works there too. > > UnixWare's Kernel is threaded, and I assume anything in libc is threadsafe > > unless > > told otherwise. > > What? You said Unixware needs getpwuid_r. And this has nothing to do > with whether the kernel is threaded. Note that Larry said "unless told otherwise", so I'm guessing that there is somewhere in Unixware taht states that standard getpwuid isn't thread safe? :)
В списке pgsql-hackers по дате отправления: