Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panicked when processing: insert at index 4 exceeds fixbitset size 2 #12819

Closed
YuanchengJiang opened this issue Oct 12, 2023 · 1 comment
Closed
Labels
type/bug Something isn't working
Milestone

Comments

@YuanchengJiang
Copy link

Describe the bug

This may related to #12818

Error message/log

No response

To Reproduce

CREATE TABLE test1 (c_0 TIMESTAMP, c_1 INT, c_2 FLOAT);
CREATE TABLE test2 (c_0 TIMESTAMP, c_1 INT, c_2 FLOAT);
SELECT max(T1.c_0) OVER(PARTITION BY T2.c_0<>T1.c_0) FROM test1 AS T1 INNER JOIN test2 AS T2 ON T1.c_0>T2.c_0 group by T1.c_0,T2.c_0;

Expected behavior

No response

How did you deploy RisingWave?

Docker

The version of RisingWave

PostgreSQL 9.5-RisingWave-1.2.0 (f27f085)

Additional context

No response

@YuanchengJiang YuanchengJiang added the type/bug Something isn't working label Oct 12, 2023
@github-actions github-actions bot added this to the release-1.4 milestone Oct 12, 2023
@xxchan
Copy link
Member

xxchan commented Oct 17, 2023

duplicate with #10666, already fixed in main

@xxchan xxchan closed this as completed Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants