From: | Philip Yarra <philip(at)utiba(dot)com> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | ECPG thread-safety |
Date: | 2003-03-28 00:44:37 |
Message-ID: | 200303281144.37663.philip@utiba.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces pgsql-patches |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-03-28 02:00:23 | Re: ECPG thread-safety |
Previous Message | Kevin Brown | 2003-03-27 22:50:01 | Re: Deadlock while doing VACUUM?? |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-03-28 02:00:23 | Re: ECPG thread-safety |
Previous Message | Bruce Momjian | 2003-03-27 18:37:40 | Re: Is PGconn* thread safe? |
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-03-28 00:53:20 | pgdump and START WITH ... |
Previous Message | Rod Taylor | 2003-03-27 22:20:24 | Re: ALTER TABLE .. SET WITH / WITHOUT OIDS |