DanRoscigno
|
6d8a2bbd48
|
standardize admonitions
|
2023-03-27 14:54:05 -04:00 |
|
Robert Schulze
|
0712627c05
|
Query cache: Fix config naming ambiguity
Add 'max_' prefix to 'size' setting to make it more clear that the cache
consumes no space if not used.
|
2023-03-24 12:52:09 +00:00 |
|
Rich Raposa
|
de68dade71
|
Revert "standardize admonitions"
|
2023-03-09 14:30:40 -07:00 |
|
DanRoscigno
|
95351bc2d3
|
standardize admonitions
|
2023-03-09 12:05:26 -05:00 |
|
Robert Schulze
|
05c5e7c73a
|
Update docs/en/operations/query-cache.md
Co-authored-by: Sergei Trifonov <sergei@clickhouse.com>
|
2023-01-31 12:44:49 +01:00 |
|
Robert Schulze
|
b268b94728
|
Update docs/en/operations/query-cache.md
Co-authored-by: Sergei Trifonov <sergei@clickhouse.com>
|
2023-01-31 12:44:38 +01:00 |
|
Robert Schulze
|
325c6bdf3d
|
Renaming: "Query Result Cache" --> "Query Cache"
Reasons:
- The cache will at some point store intermediate results as opposed to
only query results. We should change the terminology now without
having to worry about backward compat.
- Equivalent caches in MySQL (1) and Starrocks (2) are called "query
cache".
- The new name is ca. 13.8% more catchy.
(1) https://dev.mysql.com/doc/refman/5.6/en/query-cache.html
(2) https://docs.starrocks.io/en-us/2.5/using_starrocks/query_cache
|
2023-01-31 09:54:34 +00:00 |
|