From: Philip Yarra <philip@utiba.com>
To: Lee Kindness <lkindness@csl.co.uk>
Cc: Lee Kindness <lkindness@csl.co.uk>
Cc: Michael Meskes <meskes@postgresql.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ECPG thread-safety
Date: Thu, 24 Apr 2003 10:17:15 +1000
Message-ID: <200304241017.15309.philip@utiba.com> (raw)
In-Reply-To: <16038.21258.950904.455466@kelvin.csl.co.uk>
References: <200303280200.h2S20N218363@candle.pha.pa.us>
<200303281749.04746.philip@utiba.com>
<16038.21258.950904.455466@kelvin.csl.co.uk>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: philip@utiba.com, lkindness@csl.co.uk, meskes@postgresql.org
Subject: Re: ECPG thread-safety
In-Reply-To: <200304241017.15309.philip@utiba.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox