| From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | thread safety tests |
| Date: | 2004-06-09 13:13:02 |
| Message-ID: | 40C70CDE.8010109@Yahoo.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I am wondering why thread_test.c is checking for mktemp()? That function
is nowhere used in the libpq.
Also, I would suggest that we allow to build the libpq with thread
specific compiler options, even if it is not entirely thread safe. It
would require that a really multithreaded application has to have
mutexes around certain operations, but being entirely unable to
configure in a way that adds thread compile options to the CFLAGS makes
libpq completely useless for multithreaded programs on some platforms
(for example Solaris).
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-06-09 13:24:54 | Re: Improving postgresql.conf |
| Previous Message | Bruce Momjian | 2004-06-09 12:55:09 | Re: bug in 7.4 SET WITHOUT OIDs |