Re: [HACKERS] library policy question

Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)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