-
Notifications
You must be signed in to change notification settings - Fork 119
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
PostgreSQL TPROC-C consistency check 2 failed #687
Comments
In HammerDB v4.10 PostgreSQL TPROC-C consistency check 2 fails with the error:
Consistency check 2 is: For each District within a Warehouse, the value of the most recent Order ID [max(no_o_id)] minus the first Order ID [min(no_o_id)] plus one, for the NEW-ORDER table associated with the District and Warehouse, equals the number of rows in that NEW-ORDER table. That relationship can be illustrated as: max(no_o_id) – min(no_o_id) + 1 = rows in NEW-ORDER where (o_w_id = no_w_id) and (o_d_id = no_d_id) Checking the output, it can be seen that the consistency check is failing because all the values are out by 1.
This can be resolved by correcting the RETURNING d_next_o_id statement in the NEWORD stored procedure.
The fix will not impact performance between versions. |
Discussed in #686
Originally posted by mitsu-ko April 4, 2024
Hi,
I use consistency check feature in HammerDB 4.10 on PostgreSQL 15.6. Before benchmark, 'checkschema' is done without error. After running TPC-C benchmark, I run 'checkschame', consistency check fail is outputted under following.
Vuser 1 created - WAIT IDLE
Vuser 1:RUNNING
Vuser 1:Checking tpcc TPROC-C schema
Vuser 1:Check database
Vuser 1:Check tables and indices
Vuser 1:Check procedures
Vuser 1:Check consistency 1
Vuser 1:Check consistency 2
Error in Virtual User 1: TPROC-C Schema check failed tpcc schema consistency check 2 failed
Vuser 1:FINISHED FAILED
Does it means HammerDB bug or PostgreSQL bug? And I'd like to know more detail information why check is failed. It's important problem. But error message is too simple.
Regards,
The text was updated successfully, but these errors were encountered: