-
Notifications
You must be signed in to change notification settings - Fork 898
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
Assertion failure in cursor_fetcher_rewind #3786
Comments
@svenklemm can you explain what you mean by the test setup being found in #3784? That's a support issue and I cannot find anything sqlsmith-related. It would be good if you could provide proper ways to reproduce these issues instead of just copy-pasting a stack trace without a way to reproduce it. I appreciate that you've found crashes, but it is very hard to move forward on these issues with this information. Could you please provide the following:
|
@erimatnor The schema and tables are those from #3784. The query triggering the bug is in frame 34 of the stacktrace (which is mentioned in the first sentence of the ticket). Latest postgres and timescaledb version. Which extra information do you need? Did you even try to reproduce? |
@svenklemm neither @nikkhils nor @erik were able to reproduce it. If you can provide the exact setup for the to reproduce it, please do it. |
The code in in cursor_fetcher_rewind asserted that there always is an associated request which is not true if EOF was reached already. Fixes timescale#3786
The code in in cursor_fetcher_rewind asserted that there always is an associated request which is not true if EOF was reached already. Fixes timescale#3786
The code in in cursor_fetcher_rewind asserted that there always is an associated request which is not true if EOF was reached already. Fixes timescale#3786
The code in cursor_fetcher_rewind asserted that there always is an associated request which is not true if EOF was reached already. Found by sqlsmith. Fixes timescale#3786
The code in cursor_fetcher_rewind asserted that there always is an associated request which is not true if EOF was reached already. Found by sqlsmith. Fixes #3786
Query is in frame 34. Test setup is in #3784. Found by sqlsmith.
The text was updated successfully, but these errors were encountered: