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
When DEBUG4 is enabled, Citus regression tests crashes in several places #4860
Comments
Adding cherry-pick label to keep track. |
Can you share an example query which triggers the crash? |
|
Query object:
|
As seen in the previous comment, for the given query, |
Still, no idea why it only happens when |
In
|
This is what we tried on this. We basically moved the logic that extracts the column names, to However, now we are still getting crashes on later queries. And the first crash that happens, happens on Postgres' printing logic. This also makes more difficult to debug. |
Can you find a really old version of citus where we can't replicate this crash, then using binary search for commits you can find the breaking commit? |
Just a note: the example above does not seem to crash in PG13, only on PG12. It may be worth comparing the Query's produced by PG12 and PG13. |
PG 13.1, Citus master, no extra "sum":
PG 12.5, Citus master, extra "sum":
|
This also crashes even when the result of |
Another case that crashes with DEBUG4:
|
|
The crash happens on
This crashes not only for DEBUG4, but also other DEBUG levels. |
Both 2 bugs are fixed. It seems there's no other crashing case. Closing the issue. |
@agedemenli can you share the set of PRs/commits that should be backported to 10.0 releases? |
4b44e3d
Simply add the following to
src/test/regress/pg_regress_multi.pl
The text was updated successfully, but these errors were encountered: