Re: [HACKERS] --enable-thread-safety on Win32

2005-08-12 Thread Bruce Momjian
Tom Lane wrote: > "Dave Page" writes: > > However In all but one place in libpq, we don't use errno anyway > > (actually 2, but one is a bug anyway) because we use GetLastError() > > instead (which tested thread safe as well FWIW). The only place it's > > used is PQoidValue(): > > > resul

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-29 Thread Tom Lane
"Dave Page" writes: > However In all but one place in libpq, we don't use errno anyway > (actually 2, but one is a bug anyway) because we use GetLastError() > instead (which tested thread safe as well FWIW). The only place it's > used is PQoidValue(): > result = strtoul(res->cmdStatus +

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-29 Thread Dave Page
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page > Sent: 28 July 2005 16:16 > To: Bruce Momjian; Tom Lane > Cc: PostgreSQL-development > Subject: Re: [HACKERS] --enable-thread-safety on Win32 > > > >

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-28 Thread Dave Page
> -Original Message- > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > Sent: 28 July 2005 16:08 > To: Tom Lane > Cc: Dave Page; PostgreSQL-development > Subject: Re: [HACKERS] --enable-thread-safety on Win32 > > Tom Lane wrote: > > "Dave Page&

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-28 Thread Bruce Momjian
Tom Lane wrote: > "Dave Page" writes: > > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > >> 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 t

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-28 Thread Tom Lane
"Dave Page" writes: > From: Bruce Momjian [mailto:[EMAIL PROTECTED] >> 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 rathe

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-28 Thread Bruce Momjian
Dave Page wrote: > > > > -Original Message- > > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > > Sent: 28 July 2005 02:39 > > To: Dave Page > > Cc: PostgreSQL-development > > Subject: Re: [HACKERS] --enable-thread-safety on Win32 > > &g

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-28 Thread Dave Page
> -Original Message- > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > Sent: 28 July 2005 14:29 > To: Dave Page > Cc: PostgreSQL-development > Subject: Re: [HACKERS] --enable-thread-safety on Win32 > > Dave Page wrote: > > > > > > >

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-28 Thread Dave Page
> -Original Message- > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > Sent: 28 July 2005 02:39 > To: Dave Page > Cc: PostgreSQL-development > Subject: Re: [HACKERS] --enable-thread-safety on Win32 > > Dave Page wrote: > > Did anyone get a chance to

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-27 Thread Bruce Momjian
On Behalf Of Dave Page > > Sent: 21 July 2005 15:00 > > To: PostgreSQL-development > > Subject: [HACKERS] --enable-thread-safety on Win32 > > > > I've been looking into fixing the --enable-thread-safety option on > > Windows. At the moment, we have some sim

Re: [HACKERS] --enable-thread-safety on Win32

2005-07-27 Thread Dave Page
L PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Dave Page > Sent: 21 July 2005 15:00 > To: PostgreSQL-development > Subject: [HACKERS] --enable-thread-safety on Win32 > > I've been looking into fixing the --enable-thread-safety option on > Windows. At the moment, we ha

[HACKERS] --enable-thread-safety on Win32

2005-07-21 Thread Dave Page
I've been looking into fixing the --enable-thread-safety option on Windows. At the moment, we have some simple pthread emulation that may be used in libpq if --enable-thread-safety is used. The Makefile is slightly broken, however this should be easy to fix (properly) for someone more proficient w