From: Lee Kindness <lkindness@csl.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16004.6084.733022.946746@kelvin.csl.co.uk>
Date: Fri, 28 Mar 2003 09:37:08 +0000
To: Philip Yarra <philip@utiba.com>
Cc: pgsql-interfaces@postgresql.org,
	Lee Kindness <lkindness@csl.co.uk>, pgsql-hackers@postgresql.org,
	Bruce Momjian <pgman@candle.pha.pa.us>,
	Michael Meskes <meskes@postgresql.org>
Subject: ECPG thread-safety
In-Reply-To: <200303281144.37663.philip@utiba.com>
References: <200303281144.37663.philip@utiba.com>

Philip,

You can find the "patch so far" at:

 http://services.csl.co.uk/postgresql/

along with a libpq thread-safe patch.

The thread referenced by Bruce's email details some of the issues
still to be looked at. The main work is integration with the build
system (testing for and linking in POSIX threads) and testing.

I'm more than happy for you to look at at, I haven't had the time I
hoped to complete this.

Thanks, Lee.

Philip Yarra writes:
 > As I found out recently, ECPG is not thread-safe. This is a problem for us, as 
 > we really need to be able to use ECPG* in a multi-threaded C application. 
 > Michael mentioned that Lee is working on fixing these problems, but was not 
 > sure when it would be complete. 
 > 
 > So, my questions are: 
 > Lee/anyone, do you have an estimated completion date? 
 > If not, can we (myself plus a "real" C programmer) help you?
 > 
 > Regards, Philip Yarra.
 > 
 > * Yes, we could use libpq, but ECPG minimises our porting from Informix. 
 > Rewriting everything to use libpq would be too expensive.
 >