Azat Khuzhin 3a5a39a9df Do not delay final part writing by default ... For async s3 writes final part flushing was defered until all the INSERT block was processed, however in case of too many partitions/columns you may exceed max_memory_usage limit (since each stream has overhead). Introduce max_insert_delayed_streams_for_parallel_writes (with default to 1000 for S3, 0 otherwise), to avoid this. This should "Memory limit exceeded" errors in performance tests. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>		2022-03-08 22:17:36 +03:00
..
ci	Skip 01086_odbc_roundtrip for aarch, disable force_tests	2022-03-07 11:04:37 +00:00
config
fuzz
instructions	Remove PVS test	2022-02-17 12:59:47 +01:00
integration	Merge pull request #34945 from bigo-sg/hive_bug_fixed	2022-03-07 17:13:11 +01:00
jepsen.clickhouse-keeper
perf_drafts
performance	Mention scipy dep in performance bench README	2022-02-20 02:43:28 +01:00
queries	Do not delay final part writing by default	2022-03-08 22:17:36 +03:00
testflows
.gitignore
clickhouse-test	Fix clickhouse-test	2022-03-05 16:46:14 +00:00
CMakeLists.txt
msan_suppressions.txt
stress
tsan_suppressions.txt
ubsan_suppressions.txt