diff options
| author | Susan LoVerso <sue@wiredtiger.com> | 2014-06-17 13:54:11 -0400 |
|---|---|---|
| committer | Susan LoVerso <sue@wiredtiger.com> | 2014-06-17 13:54:11 -0400 |
| commit | 41ad69f2ec0c3a02d035c189d386475cbf492144 (patch) | |
| tree | 718171099027263db82ae571f6eebd07894c6662 /src/docs/threads.dox | |
| parent | 7cae375625b28b472da495aa0c852fc98908b8ec (diff) | |
| download | mongo-41ad69f2ec0c3a02d035c189d386475cbf492144.tar.gz | |
Add sentence about waiting for worker threads.
Diffstat (limited to 'src/docs/threads.dox')
| -rw-r--r-- | src/docs/threads.dox | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/docs/threads.dox b/src/docs/threads.dox index 1af182cb1d4..0d6fc7b26bd 100644 --- a/src/docs/threads.dox +++ b/src/docs/threads.dox @@ -2,7 +2,9 @@ All WT_CONNECTION methods are thread safe, and WT_CONNECTION handles can be shared between threads. Applications typically open a single -connection to each database, per process. +connection to each database, per process. Multi-threaded programs +must wait for all other threads to exit before closing the WT_CONNECTION +handle because that will implicitly close all other handles. WT_SESSION and WT_CURSOR methods are not thread safe and WT_SESSION and WT_CURSOR handles cannot be accessed concurrently by multiple threads. |