Merge branch '2.3' into 2.4

This commit is contained in:
Johan Wikman
2020-09-09 11:26:14 +03:00

View File

@ -40,7 +40,7 @@ as if the _isolation level_ would be `READ COMMITTED`, irrespective of what
the isolation level of the backends actually is. the isolation level of the backends actually is.
The default behaviour can be altered using the configuration parameter The default behaviour can be altered using the configuration parameter
[cache_inside_transactions](#cache_inside_transactions). [cache_in_transactions](#cache_in_transactions).
By default it is assumed that all `SELECT` statements are cacheable, which By default it is assumed that all `SELECT` statements are cacheable, which
means that also statements like `SELECT LOCALTIME` are cached. Please check means that also statements like `SELECT LOCALTIME` are cached. Please check
@ -282,7 +282,7 @@ the following circumstances:
Note that parsing all `SELECT` statements carries a _significant_ performance Note that parsing all `SELECT` statements carries a _significant_ performance
cost. Please read [performance](#performance) for more details. cost. Please read [performance](#performance) for more details.
#### `cache_inside_transactions` #### `cache_in_transactions`
An enumeration option specifying how the cache should behave when there An enumeration option specifying how the cache should behave when there
are active transactions: are active transactions:
@ -301,7 +301,7 @@ are active transactions:
explicitly read-only, the cache will be used and populated _until_ the explicitly read-only, the cache will be used and populated _until_ the
first non-SELECT statement. first non-SELECT statement.
``` ```
cache_inside_transactions=never cache_in_transactions=never
``` ```
Default is `all_transactions`. Default is `all_transactions`.