| 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:28:49 |
| Message-ID: | 200312160128.hBG1Sns20204@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
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(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 01:56:12 | Re: Possible bug in ECPGlib thread-safety (Postgres |
| Previous Message | Bruce Momjian | 2003-12-16 01:28:22 | Re: Possible bug in ECPGlib thread-safety (Postgres |