2021-09-19 22:38:53 +00:00
|
|
|
<clickhouse>
|
2020-07-13 15:16:34 +00:00
|
|
|
<profiles>
|
|
|
|
<default>
|
|
|
|
<max_execution_time>10</max_execution_time>
|
2023-01-08 04:57:29 +00:00
|
|
|
<max_memory_usage>10G</max_memory_usage>
|
2022-12-26 18:04:10 +00:00
|
|
|
|
2023-01-08 00:20:11 +00:00
|
|
|
<!--
|
|
|
|
Otherwise we will get the TOO_MANY_SIMULTANEOUS_QUERIES errors,
|
|
|
|
they are ok, but complicate debugging.
|
|
|
|
-->
|
|
|
|
<table_function_remote_max_addresses>200</table_function_remote_max_addresses>
|
|
|
|
|
2020-09-01 15:51:46 +00:00
|
|
|
<!--
|
|
|
|
Don't let the fuzzer change this setting (I've actually seen it
|
|
|
|
do this before).
|
|
|
|
-->
|
|
|
|
<constraints>
|
|
|
|
<max_execution_time>
|
|
|
|
<max>10</max>
|
|
|
|
</max_execution_time>
|
2021-01-06 01:07:59 +00:00
|
|
|
|
2021-01-22 00:13:47 +00:00
|
|
|
<max_memory_usage>
|
2021-01-22 14:16:08 +00:00
|
|
|
<max>10G</max>
|
2021-01-22 00:13:47 +00:00
|
|
|
</max_memory_usage>
|
2022-12-26 18:04:10 +00:00
|
|
|
|
2023-01-08 00:20:11 +00:00
|
|
|
<table_function_remote_max_addresses>
|
|
|
|
<max>200</max>
|
|
|
|
</table_function_remote_max_addresses>
|
2024-04-10 16:18:47 +00:00
|
|
|
|
|
|
|
<!-- Don't waste cycles testing the old interpreter. Spend time in the new analyzer instead -->
|
|
|
|
<allow_experimental_analyzer>
|
|
|
|
<readonly/>
|
|
|
|
</allow_experimental_analyzer>
|
2020-09-01 15:51:46 +00:00
|
|
|
</constraints>
|
2020-07-13 15:16:34 +00:00
|
|
|
</default>
|
|
|
|
</profiles>
|
2021-09-19 22:38:53 +00:00
|
|
|
</clickhouse>
|