-
Notifications
You must be signed in to change notification settings - Fork 916
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
[Bug]: Segmentation fault when INNER JOINing two hypertables #4418
Comments
@boxhock can you please share the stack trace of the crashing backend? You can use the below to get a stack trace on ubuntu: |
Hey @boxhock ... did u had a change to get a stack trace as Nikhil asked before? |
hey @boxhock any chance to provide a stack trace for us? Also, can you please share with us the exact schemes of the tables you used for reproducing the issue and maybe some sample data? These would help us to be able to constantly reproduce the issue and find the root cause. thank you. |
This issue has been automatically marked as stale due to lack of activity. You can remove the stale label or comment. Otherwise, this issue will be closed in 30 days. Thank you! |
I have the same problem on PG 14.5 with TSDB 2.8.0, getting a segfault when using I'm running Postgres in Docker, and I've no clue how to get a stack trace out of it - if someone can advise, I'd be happy to try? |
Hello @cocowalla, Thank you very much for reaching out. Creating stack traces in a Docker container can be laborious. Do you have a self-contained example that reproduces the crash that you can share? I would then try to reproduce the crash on my system and generate a stack trace. |
@jnidzwetzki I was literally just putting something together, and I saw a notification that it's fixed! What's the easiest way for me to test it before it hits v2.8.1 please? |
Easiest way is the nightly docker image: |
The latest timescaledev build is 20 days old (seems odd for a Nightly tag 😕!), so I built it myself instead. Now, the segfault is fixed, which is great! But, this issue only seems to be partially resolved - if I do an
I'll prepare a repro and create a new issue. |
@jnidzwetzki I just opened issue #4774 in relation to this |
What type of bug is this?
Crash, Unexpected error
What subsystems and features are affected?
Query executor
What happened?
I am trying to run a query on a hypertable, while also
INNER JOIN
ing it with another hypertable. However, this causes a segmentation fault. The expected behavior is for the query to complete without a segmentation fault.Changing the query to use a
LEFT JOIN
works as expected.TimescaleDB version affected
2.7.0
PostgreSQL version used
14.3
What operating system did you use?
Ubuntu 20.04.4 x86-64
What installation method did you use?
Deb/Apt
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: