--On Monday, September 01, 2003 16:01:16 -0400 Tom Lane <[EMAIL PROTECTED]> wrote:
Lee Kindness <[EMAIL PROTECTED]> writes:then how do we *PROVE* thread-safety on a particular platform?Guys, too much thought is being spent on this... 1. For the _r functions we "need" we should ALWAYS use them if the system we are building on has them - they WILL be thread-safe.
2. If the system is missing a _r function then we implement a wrapper to call the normal non-_r version. However we do NOT make this wrapper call thread-safe - we assume the non-_r version already is.
That assumption is exactly what Peter is unhappy about. With the above approach we will happily build a "thread safe" library on systems that are in fact not thread safe at all. Peter wants --enable-thread-safety to fail on non-safe systems.
In my case on UnixWare, we assume all libc is thread-safe except for those that
are specifically called out.
the getpwuid() function has a _r version, so we can use that. the gethostbyname and strerror functions do *NOT* have a _r version, but are assumed thread-safe.
The current (cvs) version can't build a thread-safe libpq, but with my patch it does build.
LER
regards, tom lane
-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
