From ac2ea9b19814a4b8379485ac8f6c1151b00c4e33 Mon Sep 17 00:00:00 2001
From: Alexey Milovidov <milovidov@yandex-team.ru>
Date: Sun, 24 Feb 2019 02:29:38 +0300
Subject: [PATCH] Added 'query_thread_log' section to configuration file. Now
 query_thread_log doesn't work without this section.

---
 dbms/programs/server/config.xml | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/dbms/programs/server/config.xml b/dbms/programs/server/config.xml
index 8a0c5be91de..154ebf6c35e 100644
--- a/dbms/programs/server/config.xml
+++ b/dbms/programs/server/config.xml
@@ -294,12 +294,20 @@
         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
     </query_log>
 
+    <!-- Query thread log. Has information about all threads participated in query execution.
+         Used only for queries with setting log_query_threads = 1. -->
+    <query_thread_log>
+        <database>system</database>
+        <table>query_thread_log</table>
+        <partition_by>toYYYYMM(event_date)</partition_by>
+        <flush_interval_milliseconds>7500</flush_interval_milliseconds>
+    </query_thread_log>
 
-    <!-- Uncomment if use part_log
+    <!-- Uncomment if use part log.
+         Part log contains information about all actions with parts in MergeTree tables (creation, deletion, merges, downloads).
     <part_log>
         <database>system</database>
         <table>part_log</table>
-
         <flush_interval_milliseconds>7500</flush_interval_milliseconds>
     </part_log>
     -->