From: | <wespvp(at)syntegra(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | joseph speigle <joe(dot)speigle(at)jklh(dot)us>, PostgreSQL <pgsql-general(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: thread_test.c problems |
Date: | 2004-04-05 04:55:57 |
Message-ID: | BC9642FD.7A2B%wespvp@syntegra.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 4/4/04 7:28 PM, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> OK, I know the cause of this. The problem is that sometimes hostnames
> don't resolve, and the bigger problem is that it requires an internet
> connection to run the tests. The attached patch tests for 'localhost'
> and your local hostname, so it should work reliably.
I did a cvs update, make, then rebuilt and tested thread_test. I ran it
about 120 times and got "GETHOSTBYNAME_THREADSAFE=yes" almost all of the
time. I got "GETHOSTBYNAME_THREADSAFE=no" three times. The other two were
always "yes".
I did verify that both the "volatile" and "localhost" changes were in there.
Dumb question... Why would you not always use the _r functions if they
exist?
Wes
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-04-05 05:43:22 | Re: thread_test.c problems |
Previous Message | Bruce Momjian | 2004-04-05 04:22:03 | Re: thread_test.c problems |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-04-05 05:43:22 | Re: thread_test.c problems |
Previous Message | Bruce Momjian | 2004-04-05 04:22:03 | Re: thread_test.c problems |