Previously we had problems parsing arithmetic operations like `b*b`.
Because of incorrect handling of the forbidden symbols in the names
we recognized `b*b` as a column name rather then a multiplication.

Arseniy Volynets authored 1 year ago and Denis Smirnov committed 11 months ago

- Detect when except, groupby, join or eqality
with subqueries is done on bucket_id column
to avoid adding extra motions

- For queries that want to join on
bucket_id column, we had wrong logic
of removing that column from child scan,
now if we have bucket_id column in
join we won't delete bucket_id from scan
node.
- Fix conflict resolution for join on
bucket_id: if we see that join is done
on bucket_id, we don't need any motions.

Note: there is still a problem when we don't
use "bucket_id" in join condition:

select t1."bucket_id", t2."bucket_id" from t1
join t2 on ...

This query will fail with error that it can't
find "bucket_id" column.

Co-authored-by: EmirVildanov <reddog201030@gmail.com>

feat: rewrite statistics structures using generic logic, add statistics merge logic, add selectivity estimation logic basement

Виталий Шунков authored 1 year ago and Denis Smirnov committed 1 year ago

NO_DOC=internal
NO_TEST=internal
NO_CHANGELOG=internal

- support parameters in form of $n like in postgres
- parameters are numbered from 1
- can't use both tarantool (?) and pg-like ($n) params
in one query