Sean Haynes 77dd869414 Add ability to log when max_partitions_per_insert_block is reached (#50948) ... * Add ability to log when max_partitions_per_insert_block is reached There's plenty of reasons to drop max_partitions_per_insert_block down from it's default of 100, with the main one being even touching remotely close to this number of partitions will create a lot of merge activity that can de-stabilise a cluster. This commit adds the ability to log when the above limit is reached rather than throw an exception, so that you can gauge the impact on users when dropping this value down. * Update docs/ru/operations/settings/query-complexity.md Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com> * Update docs/ru/operations/settings/query-complexity.md Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com> * Update docs/ru/operations/settings/query-complexity.md Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com> --------- Co-authored-by: Nikita Taranov <nickita.taranov@gmail.com>		2023-08-07 23:28:19 +02:00
..
constraints-on-settings.md
index.md
merge-tree-settings.md
permissions-for-queries.md
query-complexity.md	Add ability to log when max_partitions_per_insert_block is reached (#50948)	2023-08-07 23:28:19 +02:00
settings-profiles.md	Implemented max sessions for user	2023-07-30 22:09:03 +00:00
settings-users.md	docs	2023-05-05 22:57:48 -04:00
settings.md	Merge branch 'master' into formats-with-subcolumns	2023-08-02 15:24:56 +02:00