From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Philip Yarra <philip@utiba.com>
Cc: Demetres Pantermalis <dpant@intracom.gr>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres
Date: Mon, 15 Dec 2003 20:28:49 -0500 (EST)
Message-ID: <200312160128.hBG1Sns20204@candle.pha.pa.us> (raw)
In-Reply-To: <200312161223.30595.philip@utiba.com>
Philip Yarra wrote:
> 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?
Maybe we could just document its thread-safety as non-standard.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, philip@utiba.com, dpant@intracom.gr
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres
In-Reply-To: <200312160128.hBG1Sns20204@candle.pha.pa.us>
* 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