pin version to 11.0.1

docs/conf.py

@@ -57,9 +57,9 @@ copyright = u'2017, ' + author
 # built documents.
 #
 # The short X.Y version.
-version = u'11.0'
+version = u'11.1'
 # The full version, including alpha/beta/rc tags.
-release = u'11.0.1'
+release = u'11.1.0'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.

docs/references/configuration.rst

@@ -158,8 +158,8 @@ db-extra-search-path        String  public            Y          PGRST_DB_EXTRA_
 db-max-rows                 Int     ∞                 Y          PGRST_DB_MAX_ROWS                 pgrst.db_max_rows
 db-plan-enabled             Boolean False             Y          PGRST_DB_PLAN_ENABLED             pgrst.db_plan_enabled
 db-pool                     Int     10                           PGRST_DB_POOL
-db-pool-max-idletime        Int     30                           PGRST_DB_POOL_MAX_IDLETIME
 db-pool-acquisition-timeout Int     10                           PGRST_DB_POOL_ACQUISITION_TIMEOUT
+db-pool-max-idletime        Int     30                           PGRST_DB_POOL_MAX_IDLETIME
 db-pool-max-lifetime        Int     1800                         PGRST_DB_POOL_MAX_LIFETIME
 db-pre-request              String                    Y          PGRST_DB_PRE_REQUEST              pgrst.db_pre_request
 db-prepared-statements      Boolean True              Y          PGRST_DB_PREPARED_STATEMENTS      pgrst.db_prepared_statements
@@ -295,6 +295,13 @@ db-pool
 
   Number of maximum connections to keep open in PostgREST's database pool.
 
+.. _db-pool-acquisition-timeout:
+
+db-pool-acquisition-timeout
+---------------------------
+
+  Specifies the maximum time in seconds that the request will wait for the pool to free up a connection slot to the database.
+
 .. _db-pool-max-idletime:
 
 db-pool-max-idletime
@@ -304,13 +311,6 @@ db-pool-max-idletime
 
    Time in seconds to close idle pool connections.
 
-.. _db-pool-acquisition-timeout:
-
-db-pool-acquisition-timeout
----------------------------
-
-  Specifies the maximum time in seconds that the request will wait for the pool to free up a connection slot to the database.
-
 .. _db-pool-max-lifetime:
 
 db-pool-max-lifetime

docs/references/connection_pool.rst

@@ -15,7 +15,7 @@ Dynamic Connection Pool
 
 To conserve system resources, PostgREST uses a dynamic connection pool. This enables the number of connections in the pool to increase and decrease depending on request traffic.
 
-- If all the connections are being used, a new connection is added. The pool can grow until it reaches the :ref:`db-pool` size. Note it’s pointless to set this higher than the ``max_connections`` setting in your database.
+- If all the connections are being used, a new connection is added. The pool can grow until it reaches the :ref:`db-pool` size. Note that it’s pointless to set this higher than the ``max_connections`` setting in your database.
 - If a connection is unused for a period of time (determined by :ref:`db-pool-max-idletime`, 30 seconds by default), it will be released.
 
 Connection lifetime
@@ -25,7 +25,7 @@ Long-lived PostgreSQL connections can consume considerable memory(see `here <htt
 Under a busy system, the :ref:`db-pool-max-idletime` won't be reached and the connection pool can have many long-lived connections.
 
 To avoid this problem and save resources, a connection max lifetime (determined by :ref:`db-pool-max-lifetime`, 30 minutes by default) is enforced.
-After the max lifetime is reached, connections from the pool will be released and news ones will be created. This doesn't affect running requests, only unused connections will be released.
+After the max lifetime is reached, connections from the pool will be released and new ones will be created. This doesn't affect running requests, only unused connections will be released.
 
 Acquisition Timeout
 -------------------
@@ -68,7 +68,7 @@ Automatic Recovery
 
 The server will retry reconnecting to the database if connection loss happens.
 
-- It will retry forever with exponential backoff. 32 seconds being the maximum backoff time between retries. Each of these attempts are :ref:`logged <pgrst_logging>`.
+- It will retry forever with exponential backoff, with a maximum backoff time of 32 seconds between retries. Each of these attempts are :ref:`logged <pgrst_logging>`.
 - It will only stop retrying if the server deems the error to be fatal. This can be a password authentication failure or an internal error.
 - The retries happen immediately after a connection loss, if :ref:`db-channel-enabled` is set to true (the default). Otherwise they'll happen once a request arrives.
 - To ensure a valid state, the server reloads the :ref:`schema_cache` and :ref:`configuration` when recovering.

docs/releases/v11.1.0.rst

@@ -1,5 +1,5 @@
-Unreleased
+11.1.0
-==========
+======
 
 Features
 --------