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
Reporting WARNING after ERROR on PG15 #4837
Comments
Here is the testcase:
|
May be this is an existing issue:
|
In short this difference in the order in which WARNINGS are displayed seems to be a timing issue and an issue specific to psql utility. On server side "commit" execution flow is as follows:
On client side, as part of client-server protocol communication below is the behavior:
However on client side, sometimes the order in which WARNING/ERROR is written to console varies based on timing. Since its not timescaledb specific issue, i plan to mask the warning messages in the tests output files. A similar fix was done earlier too. Refer( commit 5fd363d). |
Testcases which kill remote processes on data nodes, tend of rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however based on timing, reports WARNINGS/ERROR in different order. Fixes timescale#4837
Testcases which kill remote processes on data nodes, tend of rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however based on timing, reports WARNINGS/ERROR in different order. Fixes timescale#4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes timescale#4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes timescale#4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes timescale#4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes timescale#4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes #4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes #4837
In remote_txn, testcases which kill remote processes on data nodes, tend to rollback transactions and as part of the process, WARNINGS/ERROR are reported to client. Client however reports WARNINGS/ERROR in different order intermittently. This is an issue specific to psql utility. Placing psql in gdb and trying to diagnise the problem does not reproduce the issue. This patch fixes the tests by not reporting WARNINGS. Fixes #4837
What type of bug is this?
Incorrect result
What subsystems and features are affected?
Other
What happened?
TimescaleDB when compiled against PG15 causes many a test to report WARNING after an ERROR.
ERROR should be the last one to be reported.
TimescaleDB version affected
2.9.0
PostgreSQL version used
15.0
What operating system did you use?
Mac OS X
What installation method did you use?
Source
What platform did you run on?
On prem/Self-hosted
Relevant log output and stack trace
No response
How can we reproduce the bug?
The text was updated successfully, but these errors were encountered: