ClickHouse/tests/queries/0_stateless/02050_client_profile_events.reference

do not print any ProfileEvents packets
0
print only last (and also number of rows to provide more info in case of failures)
[ 0 ] SelectedRows: 131010 (increment)
regression test for incorrect filtering out snapshots
0
print everything
OK
print each 100 ms
OK
check that ProfileEvents is new for each query
OK
tests: improve 02050_client_profile_events Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> 2022-04-12 17:18:27 +00:00			`do not print any ProfileEvents packets`
client: add ability to print raw profile events This can be useful for debugging and for testing (since you will not need to obtain query_id and look at query_log). v2: - mark test as long - add option to docs - add type of profile event into logs too v3: - resolve conflicts - and fix onProfileEvents callback v4: - add --print-profile-events separate switch 2021-10-12 18:03:54 +00:00			`0`
tests: improve 02050_client_profile_events Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> 2022-04-12 17:18:27 +00:00			`print only last (and also number of rows to provide more info in case of failures)`
tests: add thread_id into 02050_client_profile_events 2021-12-14 07:25:30 +00:00			`[ 0 ] SelectedRows: 131010 (increment)`
Fix filtering out snapshots from profile events This fixes POSITION_OUT_OF_BOUND error: $ clickhouse-client --print-profile-events --profile-events-delay-ms=-1 -n -q 'select sleep(1); select 1' 0 [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] ContextLock: 9 (increment) [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] FunctionExecute: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] MemoryTrackerUsage: 2132102 (gauge) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] NetworkReceiveElapsedMicroseconds: 139 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] NetworkSendBytes: 4850 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] NetworkSendElapsedMicroseconds: 1844 (increment) [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] Query: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] RWLockAcquiredReadLocks: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] SelectQuery: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] SelectedBytes: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:48 [ 0 ] SelectedRows: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] OSCPUVirtualTimeMicroseconds: 1842 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] OSReadChars: 426 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] OSWriteChars: 322 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] RealTimeMicroseconds: 1002689 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] SleepFunctionCalls: 1 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] SleepFunctionMicroseconds: 1000000 (increment) [p1.azat.localdomain] 2022.04.12 19:31:49 [ 0 ] UserTimeMicroseconds: 1843 (increment) 1 Error on processing query: Code: 11. DB::Exception: Position out of bound in Block::erase(), max position = 5. (POSITION_OUT_OF_BOUND) (version 22.4.1.1) (query: select 1) Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> 2022-04-12 16:51:39 +00:00			`regression test for incorrect filtering out snapshots`
			`0`
tests: do not use process substution in 02050_client_profile_events bash does not waits then and so if the next line will be executed fast enough, result of process substituted command can appers in stdout after it. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> 2022-04-12 17:38:16 +00:00			`print everything`
client: add ability to print raw profile events This can be useful for debugging and for testing (since you will not need to obtain query_id and look at query_log). v2: - mark test as long - add option to docs - add type of profile event into logs too v3: - resolve conflicts - and fix onProfileEvents callback v4: - add --print-profile-events separate switch 2021-10-12 18:03:54 +00:00			`OK`
tests: improve 02050_client_profile_events Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> 2022-04-12 17:18:27 +00:00			`print each 100 ms`
client: add ability to print raw profile events This can be useful for debugging and for testing (since you will not need to obtain query_id and look at query_log). v2: - mark test as long - add option to docs - add type of profile event into logs too v3: - resolve conflicts - and fix onProfileEvents callback v4: - add --print-profile-events separate switch 2021-10-12 18:03:54 +00:00			`OK`
Fix printing ProfileEvents on client for multiple queries Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com> 2022-04-11 14:42:45 +00:00			`check that ProfileEvents is new for each query`
			`OK`