From: Philip Yarra <philip@utiba.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Demetres Pantermalis <dpant@intracom.gr>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres
Date: Tue, 16 Dec 2003 12:23:30 +1100
Message-ID: <200312161223.30595.philip@utiba.com> (raw)
In-Reply-To: <200312160108.hBG18i511422@candle.pha.pa.us>
References: <200312160108.hBG18i511422@candle.pha.pa.us>
On Tue, 16 Dec 2003 12:08 pm, Bruce Momjian wrote:
> I have updated the 7.4.X does and CVS head docs to mention that ecpg SET
> CONNECTION is not thread-aware, and I have added this to the ecpg TODO:
>
> o Make SET CONNECTION thread-aware
One thing that concerns me: I doubt this is supported in other database
systems... people who relied on this feature in ECPG would likely encounter
threading bugs if they port their code to other DBs. And threading bugs can
be nasty to find. Does anyone know how other DBs handle this issue?
I thinks it's a worthy feature, but perhaps the pre-compiler should warn
people that they are relying on non-standard behaviour?
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, pgman@candle.pha.pa.us, dpant@intracom.gr
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres
In-Reply-To: <200312161223.30595.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