diff options
author | Michael Cahill <michael.cahill@mongodb.com> | 2015-11-19 16:58:50 +1100 |
---|---|---|
committer | Michael Cahill <michael.cahill@mongodb.com> | 2015-11-19 16:58:50 +1100 |
commit | 08e56e65f9f9b4129cfec2e4f6080b01dce5697e (patch) | |
tree | 9b18e198edfc30a3b10c0bb298549295cba77f3e /src | |
parent | 16c0a1abe283eb921dd670d64dd7f1520675205f (diff) | |
download | mongo-08e56e65f9f9b4129cfec2e4f6080b01dce5697e.tar.gz |
Bump the WiredTiger version to 2.7.0 in preparation for a new release.
Diffstat (limited to 'src')
-rw-r--r-- | src/docs/upgrading.dox | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/docs/upgrading.dox b/src/docs/upgrading.dox index c40e764e2f6..bda3054f644 100644 --- a/src/docs/upgrading.dox +++ b/src/docs/upgrading.dox @@ -1,6 +1,6 @@ /*! @page upgrading Upgrading WiredTiger applications -@section version_262 Upgrading to Version 2.6.2 +@section version_262 Upgrading to Version 2.7.0 <dl> <dt>Change to config_base=false</dt> @@ -26,7 +26,7 @@ WT_CURSOR::insert continued to reference application-memory specified to either WT_CURSOR::set_key or WT_CURSOR::set_value after a successful return, which could potentially lead to a core dump if the application freed that memory before a subsequent call to a WT_CURSOR:: method without an intermediate -WT_CURSOR::set_key or WT_CURSOR::set_value call. In the 2.6.2 release, +WT_CURSOR::set_key or WT_CURSOR::set_value call. In the 2.7.0 release, WT_CURSOR::insert behaves like the other cursor methods and does not reference application memory after a successful return. Applications depending on the previous semantic will require modifications to set the cursor's key and/or |