Merge pull request #10348 from ClickHouse/least-greatest-generic

Least greatest generic: more tests

tests/performance/README.md

 ## ClickHouse performance tests
 
-This directory contains `.xml`-files with performance tests for `clickhouse-performance-test` tool.
+This directory contains `.xml`-files with performance tests for @akuzm tool.
 
 ### How to write performance test
 
@@ -8,8 +8,6 @@ First of all you should check existing tests don't cover your case. If there are
 
 You have to specify `preconditions`. It contains table names. Only `hits_100m_single`, `hits_10m_single`, `test.hits` are available in CI.
 
-The most important part of test is `stop_conditions`. Also you should always specify `total_time_ms` metric. Endless tests will be ignored by CI.
-
 You can use `substitions`, `create`, `fill` and `drop` queries to prepare test. You can find examples in this folder.
 
 Take into account, that these tests will run in CI which consists of 56-cores and 512 RAM machines. Queries will be executed much faster than on local laptop.
@@ -18,9 +16,4 @@ If your test continued more than 10 minutes, please, add tag `long` to have an o
 
 ### How to run performance test
 
-You have to run clickhouse-server and after you can start testing:
-
-```
-$ clickhouse-performance-test --input-file my_lovely_test1.xml --input-file my_lovely_test2.xml
-$ clickhouse-performance-test --input-file /my_lovely_test_dir/
-```
+TODO @akuzm
\ No newline at end of file

tests/queries/0_stateless/01247_least_greatest_filimonov.reference

+2
+767
+C

tests/queries/0_stateless/01247_least_greatest_filimonov.sql

+SELECT GREATEST(2,0);
+SELECT GREATEST(34.0,3.0,5.0,767.0);
+SELECT GREATEST('B','A','C');

tests/queries/0_stateless/01248_least_greatest_mixed_const.reference

+0	6
+1	6
+2	6
+3	6
+4	6
+4	6
+4	6
+4	7
+4	8
+4	9

tests/queries/0_stateless/01248_least_greatest_mixed_const.sql

+SELECT least(4, number, 6), greatest(4, number, 6) FROM numbers(10);