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

Cache: 0 is now default of integer parameters

Browse Source 
0 is now the default of all cache configuration parameters and in
all cases the meaning is the same; that is, no limit. Internally
all limits but ttl are now for the sake of consistency 64-bit.
This commit is contained in:
Johan Wikman
2016-12-12 12:40:32 +02:00
parent e1a1c8b1cd
commit 423b54ef82
12 changed files with 120 additions and 106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
Documentation/Filters/Cache.md
View File

@ -66,9 +66,7 @@ stored in the cache. A resultset larger than this, will not be stored.
```
max_resultset_rows=1000
```
Zero or a negative value is interpreted as no limitation.
The default value is `-1`.
The default value is `0`, which means no limit.
#### `max_resultset_size`
@ -78,18 +76,17 @@ not be stored.
```
max_resultset_size=128
```
The default value is 64.
The default value is `0`, which means no limit.
#### `ttl`
_Time to live_; the amount of time - in seconds - the cached result is used
before it is refreshed from the server.
If nothing is specified, the default _ttl_ value is 10.
```
ttl=60
```
The default value is `0`, which means no limit.
#### `max_count`
@ -101,7 +98,7 @@ applied to each cache _separately_.
```
max_count=1000
```
The default value is 0, which means no limit.
The default value is `0`, which means no limit.
#### `max_size`
@ -117,7 +114,7 @@ applied to each cache _separately_.
```
max_size=1000
```
The default value is 0, which means no limit.
The default value is `0`, which means no limit.
#### `rules`