From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Philip Yarra <philip(at)utiba(dot)com> |
Cc: | Demetres Pantermalis <dpant(at)intracom(dot)gr>, pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Possible bug in ECPGlib thread-safety (Postgres |
Date: | 2003-12-16 01:58:41 |
Message-ID: | 200312160158.hBG1wf624835@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Yarra | 2003-12-16 02:11:08 | Re: Possible bug in ECPGlib thread-safety (Postgres |
Previous Message | Philip Yarra | 2003-12-16 01:56:12 | Re: Possible bug in ECPGlib thread-safety (Postgres |