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

Clarify retain_last_statements documentation

Browse Source 
Added an explicit note about usage of the retain_last_statements parameter
and that it requires dump_last_statements to work.
This commit is contained in:
Markus Mäkelä 2018-03-29 20:02:40 +03:00
parent 4167e88719
commit 177e3251ad
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Documentation/Getting-Started/Configuration-Guide.md
View File

@ -731,11 +731,16 @@ users_refresh_time=120
How many statements MaxScale should store for each session. This is for
debugging purposes, as in case of problems it is often of value to be able
to find out exactly what statements were sent before a particular
problem turned up. See also `dump_last_statements` using which the actual
dumping of the statements is enabled.
problem turned up.
**Note:** See also `dump_last_statements` using which the actual dumping
of the statements is enabled. Unless both of the parameters are defined,
the statement dumping mechanism doesn't work.
```
retain_last_statements=20
```
Default is `0`.
#### `dump_last_statements`