| From: | Philip Yarra <philip(at)utiba(dot)com> |
|---|---|
| To: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk> |
| Cc: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, Michael Meskes <meskes(at)postgresql(dot)org>, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: ECPG thread-safety |
| Date: | 2003-04-24 00:17:15 |
| Message-ID: | 200304241017.15309.philip@utiba.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces pgsql-patches |
On Wed, 23 Apr 2003 18:47, Lee Kindness wrote:
> Even with this patch you'll still be limited by the underlying
> libpq. So for example you cannot share a connection between threads
> without implementing locking to prevent multiple access to that
> connection.
Oh yes, I figured that. Each thread in this application opens its own
connection, so this ought not to be the issue. Each DB insert actually gets
the data into the table, but 2 of the 3 threads stop after that... possibly
due to concurrently accessing sections of the sqlca struct? (that's just a
guess though)
Our code is a bit tricky to get running - I might see if I can create a simple
test harness to duplicate the problem and post it to you.
Regards, Philip.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Yarra | 2003-04-24 00:24:25 | Re: ECPG thread-safety |
| Previous Message | Tom Lane | 2003-04-23 23:08:57 | Re: First draft of new FE/BE protocol spec posted for comments |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Yarra | 2003-04-24 00:24:25 | Re: ECPG thread-safety |
| Previous Message | Tom Lane | 2003-04-23 23:08:57 | Re: First draft of new FE/BE protocol spec posted for comments |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Yarra | 2003-04-24 00:24:25 | Re: ECPG thread-safety |
| Previous Message | Bruce Momjian | 2003-04-23 18:15:59 | Re: ECPG thread-safety |