-
Notifications
You must be signed in to change notification settings - Fork 668
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
[SEGFAULT] Querying distributed tables with window partition causes segmentation fault #7705
Comments
the versions used on Ubuntu 22.04 are:
and here's the stack trace for the segfault, triggered by the test described by @superbug1000 above:
|
FYI - tested with Citus 12.1 & PG 15, no segfault there. |
Also it works if the tables in question has only 1 shard
Here we face no segfault. |
Worked with @thanodnl and found that Running the same query for PG 16.1 and PG 14.5, combineQuery is same for both pg versions in the logs:
To debug further, put a breakpoint on then we can see the entire object combineQuery using pprint.
This is not a suggestion/workaround for the users facing the issue. It is for documenting what we have found, for further debugging and fixing. Now, after continuing gdb, the query should be executed without segfault, giving the correct output. Assertion failure case, in case it helps somehow: in PG14 however, this line was like Disable assertions first to get the segfault. |
Note; the removed The 3 comes from the |
Respectfully asking @thanodnl @agedemenli - any estimates for the timeline of producing a patch? |
Running the following SQL query always causes a segmentation fault in Citus 12 with Postgres 16:
The query executes successfully if:
Logs:
The text was updated successfully, but these errors were encountered: