You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Taking a quick look, it seems to me that the problem is that no_d_id and no_w_id are at indices 1 and 2 in the output of scan but are at positions 0 and 1, respectively, at the group by level.
To reproduce simply run SELECT max(no_o_id) FROM new_order GROUP BY no_d_id, no_w_id ORDER BY no_w_id, no_d_id; (against already present tpcc database) or ./cockroach workload fixtures import tpcc --warehouses=1 --db=tpcc (and that query will get executed as a part of consistency checks).
The text was updated successfully, but these errors were encountered:
yuzefovich
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
A-sql-vec
SQL vectorized engine
labels
May 6, 2019
38512: exec: fix bug in ordered aggregate planning r=jordanlewis a=jordanlewis
Previously, there was a bug that caused ordered aggregations to not be
planned correctly when some columns weren't present in the grouping
columns.
Fixes#37332.
Release note: None
Co-authored-by: Jordan Lewis <jordanthelewis@gmail.com>
When trying to import a tpcc fixture on a cluster with vectorized turned on, I ran into this crash:
Taking a quick look, it seems to me that the problem is that
no_d_id
andno_w_id
are at indices 1 and 2 in the output of scan but are at positions 0 and 1, respectively, at the group by level.To reproduce simply run
SELECT max(no_o_id) FROM new_order GROUP BY no_d_id, no_w_id ORDER BY no_w_id, no_d_id;
(against already presenttpcc
database) or./cockroach workload fixtures import tpcc --warehouses=1 --db=tpcc
(and that query will get executed as a part of consistency checks).The text was updated successfully, but these errors were encountered: