11 Commits

Author	SHA1	Message	Date
Maksim Kita	5ef83deaa6	Update sort to pdqsort	2022-01-30 19:49:48 +00:00
Alexey Milovidov	dbff1edcd3	Fix memory tracking of aggregate function topK	2021-06-14 05:26:05 +03:00
Alexey Milovidov	c7b6d3e2ac	PVS-Studio	2021-05-03 18:25:14 +03:00
Alexey Milovidov	9f74565948	PVS-Studio	2021-05-03 01:42:01 +03:00
Alexey Milovidov	093108bf81	Normalize BigInt implementation	2021-01-27 03:54:57 +03:00
Maksim Kita	bf5d75853c	Added erase into HashTable	2020-12-11 16:54:08 +03:00
Maksim Kita	d8b78682e1	SpaceSaving remove last element from map fix	2020-12-11 16:54:08 +03:00
Alexey Milovidov	1cee6d5a31	Check for array size overflow in topK #14452	2020-09-04 04:05:57 +03:00
Alexander Kuzmenkov	7142e68d7a	fixup	2020-05-26 08:54:04 +03:00
Alexander Kuzmenkov	50df893dc6	Assert that allocator & container are consistent wrt. inline memory ... There are lots of places where HashTable is used with AllocatorWithStackMemory, but the size of allocator inline memory is set incorrectly, and it's less than the initial HashTable buffer size. Because of this, HashTable is always allocated on the heap, and the inline memory becomes a useless dead weight. For PODArray, we have previously added a helper template that makes sure these values are in sync, so there was only one such discrepancy left, in the unit test.	2020-05-20 22:37:13 +03:00
Ivan Lezhankin	06446b4f08	dbms/ → src/	2020-04-03 18:14:31 +03:00