Remove the potential state transition from 1 to 0.
Signed-off-by: Matt Kangas <firstname.lastname@example.org>
…ript Signed-off-by: Matt Kangas <email@example.com>
…conflicts (via 2.4.9)
(cherry picked from commit ea2102c)
…NamespaceString to std::string. By replacing the implicit conversion operator from const NamespaceString&->std::string with one from const NamespaceString&->const std::string&, we at least eliminate an implicit copy. Better might be to get rid of the implicit conversion entirely, but we might want to start by removing APIs that take std::string when they mean NamespaceString.
This change removes all usages of LockStatus and pushes the lock acquisitions to be inside the respective commands. This is a refactoring on the way to per-document locking.
…ng work() on the child Doing so could cause missing results for a tailable cursor.
The following change was backported: https://code.google.com/p/gperftools/source/detail?r=18fbc316eebea9db2d7ec41e161c0a3fbb09fa42 Another change we wanted was: https://code.google.com/p/gperftools/source/detail?r=6287bbbbad8730712cfd1ee28ecc0648cbaa9f94# However, since that patch must hit every PR/SC instance and the code has evolved from that point we instead just ran the following two scripts over the gperftools source tree: find . -type f | xargs egrep -l '"PR\w+"' | xargs perl -pi -e 's|"PR(\w+)"|" PR\1 "|g' find . -type f | xargs egrep -l '"SC\w+"' | xargs perl -pi -e 's|"SC(\w+)"|" SC\1 "|g' and then manually fixing up the one reference to GPRIuPTHREAD, which achieved the same result. Finally, remove the logic preventing mixture of C++11 and gperftools from the build system.