| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | "Shridhar Daithankar<shridhar_daithankar(at)persistent(dot)co(dot)in>" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ECPG, threading and pooling |
| Date: | 2003-01-23 15:10:09 |
| Message-ID: | 20030123151009.GA8056@feivel.fam-meskes.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Thu, Jan 23, 2003 at 02:40:33PM +0530, Shridhar Daithankar<shridhar_daithankar(at)persistent(dot)co(dot)in> wrote:
> I would like to use ECPG as it is relatively easy to code. However my
> application is multithreaded and also uses connecion pools.
I'm afraid it needs some work to be thread-safe. sqlca is defined
statically. No big deal it seems to implement a thread safe version but
I haven't yet found the time.
> I would like to know if ECPG is thread safe and I can use an arbitrary PGconn*
> object pulled from a connection pool.
Not sure what you mean with this?
> Do I need to use connection name? I mean how do I store connection name in an
> array or so?
How else would you decide against whcih connection to run the statement?
Michael
--
Michael Meskes
Email: Michael(at)Fam-Meskes(dot)De
ICQ: 179140304
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Wampler | 2003-01-23 15:12:10 | Re: Threads |
| Previous Message | Tom Lane | 2003-01-23 15:03:28 | Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shridhar Daithankar | 2003-01-23 15:28:24 | Re: ECPG, threading and pooling |
| Previous Message | Shridhar Daithankar<shridhar_daithankar@persistent.co.in> | 2003-01-23 09:10:33 | ECPG, threading and pooling |