Re: [HACKERS] library policy question - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] library policy question
Date
Msg-id 26519.952544972@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] library policy question  (Thomas Lockhart <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
>> And what shall I do with sqlca? Make every program define it in its own 
>> space?

> My vague recollection is that embedded SQL doesn't multithread very
> well for exactly this reason. You may be stuck with a global variable
> for that case...

Aside from the unthreadable API, ecpg has another potential threading
problem: it depends on a lexer and parser that might or might not be
thread-safe, depending on what they were generated with.

I'd advise just labeling ecpg "not threadable" :-(.  Not much point in
breaking existing apps by changing the API, when you still won't be able
to guarantee thread safeness...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Regression test failure (runcheck)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Transaction abortions & recovery handling