diff --git a/docs/references/connection_pool.rst b/docs/references/connection_pool.rst index 74385b225..fe68501d0 100644 --- a/docs/references/connection_pool.rst +++ b/docs/references/connection_pool.rst @@ -47,6 +47,8 @@ Under a busy system, the :ref:`db-pool-max-idletime` won't be reached and the co To avoid this problem and save resources, a connection max lifetime (:ref:`db-pool-max-lifetime`) is enforced. 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. +.. _pool_timeout: + Acquisition Timeout ------------------- diff --git a/docs/references/schema_cache.rst b/docs/references/schema_cache.rst index deb053181..c94b7de7c 100644 --- a/docs/references/schema_cache.rst +++ b/docs/references/schema_cache.rst @@ -24,7 +24,7 @@ You can do this with UNIX signals or with PostgreSQL notifications. It's also po .. note:: - - Requests will wait until the schema cache reload is done. This to prevent client errors due to an stale schema cache. + - If the schema cache fails to reload (e.g. due to a ``statement_timeout`` or :ref:`pool timeout `), PostgREST will continue serving requests in a "best effort" basis. - If you are using the :ref:`in_db_config`, a schema cache reload will :ref:`reload the configuration` as well. .. _schema_reloading_signals: