Subject | Firebird Embedded 2.1 Thread Safety |
---|---|
Author | Stefan Schultze |
Post date | 2009-08-27T15:52:57Z |
Hi,
I always thought Firebird Embedded 2.1 (Windows) is thread-safe (if
connections are not accessed by multiple threads at a time), as stated in
many mailing list posts and here:
http://www.firebirdsql.org/devel/python/docs/3.3.0/thread-safety-overview.ht
ml
Now, the Beta 2.5 release notes say that "The embedded libraries [...]
fbembed.dll on Windows - are now multi-threadcapable and thread-safe, so
they can be used in multi-threaded applications."
I'm confused what this means for v2.1 - does it mean that it was absolutely
not thread-safe in the past but it is now (in 2.5 Beta), or does it mean
that things just improved a bit (e.g. I can now access the same connection
from multiple threads at the same time)?
We do internal load tests with 200+ threads over many days and have never
seen any problem with concurrent access to Firebird Embedded 2.1.
Thanks in advance.
Stefan
I always thought Firebird Embedded 2.1 (Windows) is thread-safe (if
connections are not accessed by multiple threads at a time), as stated in
many mailing list posts and here:
http://www.firebirdsql.org/devel/python/docs/3.3.0/thread-safety-overview.ht
ml
Now, the Beta 2.5 release notes say that "The embedded libraries [...]
fbembed.dll on Windows - are now multi-threadcapable and thread-safe, so
they can be used in multi-threaded applications."
I'm confused what this means for v2.1 - does it mean that it was absolutely
not thread-safe in the past but it is now (in 2.5 Beta), or does it mean
that things just improved a bit (e.g. I can now access the same connection
from multiple threads at the same time)?
We do internal load tests with 200+ threads over many days and have never
seen any problem with concurrent access to Firebird Embedded 2.1.
Thanks in advance.
Stefan