hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

MXS-1474 Update cache documentation

Browse Source
This commit is contained in:
Johan Wikman
2017-10-25 10:08:36 +03:00
parent cb5c22269e
commit 5068d49cf7
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/Filters/Cache.md
View File

@ -22,6 +22,10 @@ been started with `BEGIN`, `START TRANSACTION` or `START TRANSACTION READ
WRITE`, then the cache will be used and populated until the first `UPDATE`,
`INSERT` or `DELETE` statement is encountered.
That is, in default mode the cache effectively causes the system to behave
as if the _isolation level_ would be `READ COMMITTED`, irrespective of what
the isolation level of the backends actually is.
The default behaviour can be altered using the configuration parameter
[cache_inside_transactions](#cache_inside_transactions).
@ -264,11 +268,9 @@ are active transactions:
The cache will be populated if the transaction is explicitly read only
or if no non-SELECT statement has been encounted.
* `read_only_transactions`: The cache will be used and populated inside
_explicitly_ read-only transactions. If the transaction is not explicitly
read only, the cache will be populated (but not used) until the first
non-SELECT statement.
_explicitly_ read-only transactions.
* `all_transactions`: The cache will be used and populated inside
explicitly read-only transactions. Inside transactions that are not
_explicitly_ read-only transactions. Inside transactions that are not
explicitly read-only, the cache will be used and populated _until_ the
first non-SELECT statement.
```