ClickHouse/tests/queries/0_stateless/00612_pk_in_tuple_perf.reference

1
		"rows_read": 2,
1
		"rows_read": 2,
Try fix pk in tuple performance Possible approach for fixing #10574 The problem is that prepared sets are built correctly, it is a hash map of key -> set where key is a hash of AST and list of data types (when we a list of tuples of literals). However, when the key is built from the index to try and find if there exists a prepared set that would match it looks for data types of the primary key (see how data_types is populated) because the primary key has only one field (v in my example) it can not find the prepared set. The patch looks for any prepared indexes where data types match for the subset of fields found in primary key, we are not interested in other fields anyway for the purpose of primary key pruning. 2020-06-30 15:33:16 +00:00			`1`
			`"rows_read": 2,`
Add a test to cover non-const tuple elemenets (just in case) 2020-07-01 10:01:47 +00:00			`1`
			`"rows_read": 2,`