Skip site navigation (1) Skip section navigation (2)

Re: Libpq driver: thread problem

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-odbc(at)postgresql(dot)org,Anoop Kumar <anoopk(at)pervasive-postgres(dot)com>
Subject: Re: Libpq driver: thread problem
Date: 2005-07-14 16:02:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
Dave Page wrote:
> > -----Original Message-----
> > From: pgsql-odbc-owner(at)postgresql(dot)org 
> > [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Dave Page
> > Sent: 14 July 2005 12:06
> > To: pgsql-odbc(at)postgresql(dot)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                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-odbc by date

Next:From: Dave PageDate: 2005-07-14 16:13:36
Subject: Re: Libpq driver: thread problem
Previous:From: Joel FradkinDate: 2005-07-14 15:45:59
Subject: Re: Benchmark results

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group