Dave Page wrote:
>
>
> > -----Original Message-----
> > From: pgsql-odbc-owner@postgresql.org
> > [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Dave Page
> > Sent: 14 July 2005 12:06
> > To: pgsql-odbc@postgresql.org
> > Cc: Anoop Kumar
> > Subject: [ODBC] Libpq driver: thread problem
> >
> > One thing to note, the Windows Port of PostgreSQL has never
> > worked with
> > the --enable-thread-safety option. This has never been a problem for
> > pgAdmin (for example), but may be here.
>
> After some discussion with Magnus Hagander, that is probably a red
> herring. He recalls that --enable-thread-safety is needed on platforms
> that don't have a thread safe API already - windows does as I'm sure you
> know.
I don't think that is correct --- you do need that flag for libpq to be
thread safe. If the thread flag doesn't work on Win32, we need to fix
it. I know we applies some patches during 8.0 beta so it _should_ work,
and if it doesn't we need to add it to the TODO list or fix it.
The main issue with the flag, as I remember, is to allow multiple
threads to open libpq connections. If you don't do that, you don't need
the flag.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
