Re: [GENERAL] libpy and ENABLE_THREAD_SAFETY=1

2005-08-17 Thread Pit Müller
Magnus Hagander wrote: Is the standard libpq.dll distributed by PostgreSQL8.0 for windows thread safe by default ? No. It is safe as long as you use each PGconn on a separate thread but you cannot share the same PGconn between threads. //Magnus But what if I compile the DLL using E

Re: [GENERAL] libpy and ENABLE_THREAD_SAFETY=1

2005-08-17 Thread Pit Müller
Magnus Hagander wrote: Is the standard libpq.dll distributed by PostgreSQL8.0 for windows thread safe by default ? No. It is safe as long as you use each PGconn on a separate thread but you cannot share the same PGconn between threads. //Magnus But what

Re: [GENERAL] libpy and ENABLE_THREAD_SAFETY=1

2005-08-16 Thread Magnus Hagander
> >In theory, but I beleive there are build issues in the currently > >released version when it comes to building on win32 with > >ENABLE_THREAD_SAFETY. > > > >//Magnus > > > > > > > > > Thank you for this information. > > Your wrote: "In theory" > Do you know anybody who has tested this ? >

Re: [GENERAL] libpy and ENABLE_THREAD_SAFETY=1

2005-08-15 Thread Magnus Hagander
> >>Is the standard libpq.dll distributed by PostgreSQL8.0 for windows > >>thread safe by default ? > >> > >> > > > >No. > >It is safe as long as you use each PGconn on a separate > thread but you > >cannot share the same PGconn between threads. > > > >//Magnus > > > > > > > > > But what i

Re: [GENERAL] libpy and ENABLE_THREAD_SAFETY=1

2005-08-10 Thread Magnus Hagander
> Is the standard libpq.dll distributed by PostgreSQL8.0 for > windows thread safe by default ? No. It is safe as long as you use each PGconn on a separate thread but you cannot share the same PGconn between threads. //Magnus ---(end of broadcast)

[GENERAL] libpy and ENABLE_THREAD_SAFETY=1

2005-08-10 Thread Pit M.
Is the standard libpq.dll distributed by PostgreSQL8.0 for windows thread safe by default ? Pit ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings