From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200312160128.hBG1SMr20109@candle.pha.pa.us>
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres
In-Reply-To: <200312161223.30595.philip@utiba.com>
To: Philip Yarra <philip@utiba.com>
Date: Mon, 15 Dec 2003 20:28:22 -0500 (EST)
Cc: Demetres Pantermalis <dpant@intracom.gr>, pgsql-interfaces@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII

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?

It would cause people moving _from_ PostgreSQL, but no one does that, of
course.  :-)

I thought the standard wasn't clear so we could do it.  You have a good
point, but that AT clause is annoying people.   Other comments?  

-- 
  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