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

Re: Libpq driver: thread problem

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "Marko Ristola" <Marko(dot)Ristola(at)kolumbus(dot)fi>,<pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Libpq driver: thread problem
Date: 2005-08-12 21:38:28
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC99E7@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-odbc
 

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman(at)candle(dot)pha(dot)pa(dot)us] 
> Sent: 12 August 2005 22:25
> To: Dave Page
> Cc: Marko Ristola; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Libpq driver: thread problem
> 
> Dave Page wrote:
> > Err, what's been saved? This is part of a discussion re psqlODBC -
> > there's no patches here yet, and any that do come of it will be for
> > psqlODBC, not the server.
> 
> Uh, doesn't libpq have the same issue?

Setlocale() doesn't appear to be used in libpq afaics (unless it's used
in some external macro or function I haven't found).

Besides, the problem being discussed in the thread turned out to be a
logic error in the LIBPQ_Execute function in the driver. Once I tracked
it down, it worked perfectly.

Regards, Dave.

Responses

pgsql-odbc by date

Next:From: Tom LaneDate: 2005-08-12 21:39:08
Subject: Re: Libpq driver: thread problem
Previous:From: Bruce MomjianDate: 2005-08-12 21:24:40
Subject: Re: Libpq driver: thread problem

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