I looked for another thread-unsafe usage of variables like prep_stmts,
and I found the 4 possibly-unsafe ones:
 all_descriptors in ecpg/ecpglib/descriptor.c:
Management of descriptors used by SQL DESCRIPTOR is not safe.
 auto_allocs in ecpg/ecpglib/memory.c:
All memory allocation for statements are not safe.
 nextStmtID in ecpg/ecpglib/prepare.c:
Increment is not safe in ECPGauto_prepare().
 stmtCacheEntries in ecpg/ecpglib/prepare.c:
Reading/writing are not safe in ECPGauto_prepare().
I'm not convinced that all of the above are completely dangerous,
but  might affect all of users writing multi-threaded ecpg programs...
Are there any bugs we should fix?
NTT Open Source Software Center
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2007-09-26 09:13:06|
|Subject: Re: SetBufferCommitInfoNeedsSave and race conditions|
|Previous:||From: Stefan Kaltenbrunner||Date: 2007-09-26 08:54:07|
|Subject: Re: pgcrypto & strong ciphers limitation|