X-Original-To: pgsql-interfaces@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5DC1347580B for ; Thu, 27 Mar 2003 19:50:55 -0500 (EST) Received: from cpc-gw2.cpc.net.au (unknown [210.9.248.93]) by postgresql.org (Postfix) with ESMTP id EF5C4474E44 for ; Thu, 27 Mar 2003 19:50:53 -0500 (EST) Received: from utiba.com (IDENT:root@ser1.cpc.net.au [192.168.0.19]) by (Utiba Mail Thingy 2/1.1.3) with ESMTP id h2RNj6Z20531 for ; Fri, 28 Mar 2003 10:45:06 +1100 Received: from Utiba Mail Thingy by utiba.com (Dunno/1.1.2) with ESMTP id LAA22426 for ; Fri, 28 Mar 2003 11:50:55 +1100 Content-Type: text/plain; charset="us-ascii" From: Philip Yarra Organization: Utiba To: pgsql-interfaces@postgresql.org Subject: ECPG thread-safety Date: Fri, 28 Mar 2003 11:44:37 +1100 User-Agent: KMail/1.4.1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200303281144.37663.philip@utiba.com> X-Spam-Status: No, hits=-12.2 required=5.0 tests=BAYES_10,USER_AGENT_KMAIL autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200303/168 X-Sequence-Number: 3917 As I found out recently, ECPG is not thread-safe. This is a problem for us,= as=20 we really need to be able to use ECPG* in a multi-threaded C application.= =20 Michael mentioned that Lee is working on fixing these problems, but was not= =20 sure when it would be complete.=20 So, my questions are:=20 Lee/anyone, do you have an estimated completion date?=20 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.=20 Rewriting everything to use libpq would be too expensive.