- 27 10月, 2020 1 次提交
-
-
由 kssenii 提交于
-
- 25 10月, 2020 5 次提交
-
-
由 Ivan 提交于
* Use only |name_parts| as primary name source * Restore legacy logic for table restoration * Fix build * Fix tests * Add pytest server config * Fix tests * Fixes due to review
-
由 alexey-milovidov 提交于
minor fix.
-
由 alexey-milovidov 提交于
Significantly decrease MemoryTracking drift
-
由 alexey-milovidov 提交于
-
由 alexey-milovidov 提交于
-
- 24 10月, 2020 34 次提交
-
-
由 Nikita Mikhaylov 提交于
Student and Welch t-test
-
由 Xianda Ke 提交于
redundant variable, duplicated defination of the variable aad_data compiler error: variable ‘aad_value’ set but not used [-Werror=unused-but-set-variable]
-
由 alexey-milovidov 提交于
try use cmake version for croaring instead of amalgamation.sh
-
由 alexey-milovidov 提交于
Add check for BOM
-
由 Alexey Milovidov 提交于
-
由 Azat Khuzhin 提交于
-
由 alexey-milovidov 提交于
Revert "Optionally upload clickhouse binary in fast test"
-
由 alexey-milovidov 提交于
-
由 alexey-milovidov 提交于
Database or Table Engine description template update
-
由 alexey-milovidov 提交于
Change error message in function if & ifNull
-
由 alexey-milovidov 提交于
Add more context to error messages
-
由 alexey-milovidov 提交于
Optionally upload clickhouse binary in fast test
-
由 alexey-milovidov 提交于
Add total_rows/total_bytes support for Set/Join
-
由 alexey-milovidov 提交于
Add ability to specify PRIMARY KEY without ORDER BY
-
由 sundy-li 提交于
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
01540_MemoryTracking is failing on CI for the following reasons: - log_queries (fixed, by adding log_queries=0) - profilers (fixed) - but what can't be fixed is metric_log and so on, so we need separate instance with separate configuration (sigh).
-
由 alexey-milovidov 提交于
Fix broken link in replication docs
-
由 alexey-milovidov 提交于
Fix TwoLevelStringHashTable bug
-
由 Alexey Milovidov 提交于
-
由 tavplubix 提交于
Fixes for DDL queries
-
由 nikitamikhaylov 提交于
-
由 nikitamikhaylov 提交于
-
由 tavplubix 提交于
Atomic DROP DATABASE SYNC
-
由 Azat Khuzhin 提交于
-
由 tavplubix 提交于
-
由 tavplubix 提交于
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
v2: disable query profiling and logging in 01540_MemoryTracking (This should make MemoryTracker drift zero).
-
由 Azat Khuzhin 提交于
-
由 Azat Khuzhin 提交于
MemoryTracker assumes that for VariableContext::Thread new/delete may be called from different threads, hence the amount of memory can go negative. However the MemoryTracker is nested, so even if the negative amount is allowed for VariableContext::Thread it does not allowed for anything upper, and hence the MemoryTracking will not be decremented properly. Fix this, by passing initial size to the parent free. This should fix memory drift for HTTP queries.
-
由 Azat Khuzhin 提交于
This should significantly reduce the MemoryTracking drift, test shows that there is 0 drift after query storm (100 queries, via http/tcp/tcp in one session). TL;DR; To track memory, clickhouse creates memory tracker object for each thread **explicitly**, but until it is not created the memory allocations are not under account. There should not be lot of allocations w/o memory tracker, since most of the time it is created early enough, but even this maybe enough to trigger some problems. Plus sometimes it is not possible to create it, for example some 3d party library does not allow to do this explicitly: - for example before #15740 allocations from librdkafka threads, - or even worse, poco threads, they don't have any routines to do this. This won't be a problem for `MemoryTracking` metric if the deallocation will be done from the same thread w/o memory tracker (or vise versa), but this is not always true. NOTE, that this will slow down per-thread allocations w/o memory tracker, since before this patch there were no memory tracking for them while now they will be accounted in total_memory_tracker, and for total_memory_tracker max_untracked_memory is always reached. But this should not be significant.
-
由 alexey-milovidov 提交于
Link dbms w/ atomic to fix undefined reference in unbundled build
-
由 alesapin 提交于
-