Re: [GENERAL] thread_test.c problems

2004-04-04 Thread Bruce Momjian
Bruce Momjian wrote: > > 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". > > Yep, I can reproduce

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread Bruce Momjian
[EMAIL PROTECTED] wrote: > On 4/4/04 7:28 PM, "Bruce Momjian" <[EMAIL PROTECTED]> 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

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread wespvp
On 4/4/04 7:28 PM, "Bruce Momjian" <[EMAIL PROTECTED]> 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 h

Re: [GENERAL] RPM init-script: Why the locale setting?

2004-04-04 Thread Tom Lane
Troels Arvin <[EMAIL PROTECTED]> writes: > In the init-script contained in the RPMs downloadable from the PostgreSQL > site (I checked the one for Fedora), an explicit locale is set before > running initdb. - And the explicit locale is not "C". Only if you don't have a sysconfig file: # J

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > [EMAIL PROTECTED] wrote: > > have you tried adding a volatile keyword to the > > int volatile errno1_set = 0; > > int volatile errno2_set = 0; > > > > I have applied the following patch to CVS head which does a getpid() in > > the loo

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] wrote: > have you tried adding a volatile keyword to the > int volatile errno1_set = 0; > int volatile errno2_set = 0; > > I have applied the following patch to CVS head which does a getpid() in > the loop, rather than nothing. That do

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread Bruce Momjian
[EMAIL PROTECTED] wrote: > Add this to your template/$port file: > > STRERROR_THREADSAFE=yes > GETPWUID_THREADSAFE=yes > GETHOSTBYNAME_THREADSAFE=no > > [g4:src/tools/thread] wp% ./thread_test > Make sure you have added any needed 'THREAD_CPPFLAGS' and 'THREAD_LIBS' > defines to your template/$po

Re: [GENERAL] RPM init-script: Why the locale setting?

2004-04-04 Thread Stephan Szabo
On Sun, 4 Apr 2004, Troels Arvin wrote: > Hello, > > In the init-script contained in the RPMs downloadable from the PostgreSQL > site (I checked the one for Fedora), an explicit locale is set before > running initdb. - And the explicit locale is not "C". > > This means that a PostgreSQL installati

[GENERAL] Version 1.0.0.4 released

2004-04-04 Thread Shachar Shemesh
Hi all, Version 1.0.0.4 of the Postgresql OLE DB provider for Windows was just released. Get it at http://gborg.postgresql.org/project/oledb/download/download.php?branch=devel. Release includes a source only version, and a compiled version. The compiled version will require libpq (precompiled

Re: [GENERAL] RPM init-script: Why the locale setting?

2004-04-04 Thread Paul Thomas
On 04/04/2004 21:48 Troels Arvin wrote: Hello, In the init-script contained in the RPMs downloadable from the PostgreSQL site (I checked the one for Fedora), an explicit locale is set before running initdb. - And the explicit locale is not "C". This means that a PostgreSQL installation will not us

[GENERAL] RPM init-script: Why the locale setting?

2004-04-04 Thread Troels Arvin
Hello, In the init-script contained in the RPMs downloadable from the PostgreSQL site (I checked the one for Fedora), an explicit locale is set before running initdb. - And the explicit locale is not "C". This means that a PostgreSQL installation will not use indexes for LIKE queries (I just ran

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread wespvp
> I have applied the following patch to CVS head which does a getpid() in > the loop, rather than nothing. getpid() should force a system call, > which will make it more likely for the other thread to get CPU time and > complete its tests. Works for me... However, there seems to be a reliability

Re: [GENERAL] thread_test.c problems

2004-04-04 Thread Bruce Momjian
[EMAIL PROTECTED] wrote: > On 4/4/04 12:33 AM, "joseph speigle" <[EMAIL PROTECTED]> wrote: > > > have you tried adding a volatile keyword to the > > > > int volatile errno1_set = 0; > > int volatile errno2_set = 0; > > > > that should stop while-loop optimizing for cases where the variable is >