Re: thread_test.c problems

> OK, I just did some major wacking of the thread stuff and tried it on
> FreeBSD 4.9. It failed because getpwuid() isn't thread-safe on that
> platform, and there isn't a getpwuid_r() function, but it did pick up
> -pthread as a valid option.
>
> Please test CVS HEAD and report back. Thanks.

Maybe -lpthread isn't needed on OS X (10.3)? I built thread_test, which
compiled without -lpthread and still worked. How can I be certain
postgresql built correctly with full thread support?

% make
gcc -no-cpp-precomp -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -D_REENTRANT -D_THREAD_SAFE
-D_POSIX_PTHREAD_SEMANTICS -I../../../src/include -c -o thread_test.o
thread_test.c -MMD
gcc -no-cpp-precomp -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes
-Wmissing-declarations -D_REENTRANT -D_THREAD_SAFE
-D_POSIX_PTHREAD_SEMANTICS -L../../../src/port thread_test.o -o
thread_test

% otool -L thread_test (Apple technote says this is the same as "ldd")
thread_test:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 71.0.0)

% ./thread_test
Your errno is thread-safe.
Your system has sterror_r(); it does not need strerror().
Your system has getpwuid_r(); it does not need getpwuid().
Your system has getaddrinfo(); it does not need gethostbyname()
or gethostbyname_r().

Your platform is thread-safe.