From: Bruce Momjian <pgman@candle.pha.pa.us>
Message-Id: <200312160158.hBG1wf624835@candle.pha.pa.us>
Subject: Re: Possible bug in ECPGlib thread-safety (Postgres
In-Reply-To: <200312161256.12516.philip@utiba.com>
To: Philip Yarra <philip@utiba.com>
Date: Mon, 15 Dec 2003 20:58:41 -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:28 pm, Bruce Momjian wrote:
> > > 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.
> 
> Yes, but my concern is that poor suckers who try to port their code to other 
> DBs won't be going and reading the PostgreSQL doco to figure out why their 
> code goes suddenly goes "thud!"
> 
> Maybe an additional flag for the pre-compiler to turn the warning off (how 
> about '--fast-and-loose-thread-behaviour', '-f' for short ?) would stop it 
> driving regular users mad, while alerting newer ECPG users that they are 
> relying on an extension that might cause portability issues. 

I don't think we are going to accept annoying our users on every
compile.

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