From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: --enable-thread-safety on Win32 |
Date: | 2005-07-28 14:44:36 |
Message-ID: | 23922.1122561876@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us]
>> I would like to see how hard it would be to
>> add #ifdefs to get the test program to run on Win32.
> I did manage to get it to compile (though not work fully just yet),
> however I had to use the full pthreads library rather than our minimal
> implementation. That's why I question whether we should go this way - an
> extra dependency (pthreads is not normally on a Windows box, even with
> Msys) to test an OS that we know 100% for sure is not going to vary in
> it's thread-safetyness(!) from system to system.
I agree --- that seems like useless make-work. Just put a special case
for Windows into configure.in and be done with it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-07-28 15:08:12 | Re: --enable-thread-safety on Win32 |
Previous Message | Dave Page | 2005-07-28 13:36:07 | Re: --enable-thread-safety on Win32 |