aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGaurish Sharma <contact@gaurishsharma.com>2014-02-10 00:53:51 +0530
committerGaurish Sharma <contact@gaurishsharma.com>2014-02-10 00:53:51 +0530
commit395bcb5cfc516870bb9ba53e776a3ac70eea4952 (patch)
tree5384c70b1dfad6f9ad602990eee80b65fa2d496a
parent72e11abeaf6500fa81ee2260fa446fcabcc2a944 (diff)
downloadrails-395bcb5cfc516870bb9ba53e776a3ac70eea4952.tar.gz
rails-395bcb5cfc516870bb9ba53e776a3ac70eea4952.tar.bz2
rails-395bcb5cfc516870bb9ba53e776a3ac70eea4952.zip
`Rails.threadsafe!` mode is deprecated
[ci skip]
-rw-r--r--guides/source/configuring.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/configuring.md b/guides/source/configuring.md
index d3bd5c1c18..7b72e27b96 100644
--- a/guides/source/configuring.md
+++ b/guides/source/configuring.md
@@ -939,4 +939,4 @@ ActiveRecord::ConnectionTimeoutError - could not obtain a database connection wi
If you get the above error, you might want to increase the size of connection
pool by incrementing the `pool` option in `database.yml`
-NOTE. If you have enabled `Rails.threadsafe!` mode then there could be a chance that several threads may be accessing multiple connections simultaneously. So depending on your current request load, you could very well have multiple threads contending for a limited amount of connections.
+NOTE. As Rails is multi-threaded by default, there could be a chance that several threads may be accessing multiple connections simultaneously. So depending on your current request load, you could very well have multiple threads contending for a limited amount of connections.