Open qvad opened 4 months ago
After running few experiments found one cause of this issue - adding datatype casting to reads make workload fail on transactional validation checks, i.e. even INT datatype could fail. Changed issue description
SELECT SUM(%s)::bigint FROM %s
SELECT %s::bigint FROM %s WHERE id = %s
Jira Link: DB-12135
Description
In classic bank workload we added datatypes support to extend coverage for existing features. E.g. now there are varchars, dates, timestamps and json support.
Balance selection: JSON -
SELECT (SUBSTRING((%s->'content'->>'value') FROM ':(.*?)(:|$)'))::bigint AS balance FROM %s WHERE id = %
Varchar -SELECT (SUBSTRING(%s FROM ':(.*?)(:|$)'))::bigint FROM %s WHERE id = %s
Money -SELECT %s::numeric::integer FROM %s WHERE id = %s
Timestamp -SELECT EXTRACT(MILLISECONDS FROM %s) AS epoch_days FROM %s WHERE id = %s
Date -SELECT (EXTRACT(EPOCH FROM %s) / 86400) AS sum_of_epoch_days FROM %s WHERE id = %s
Note that due to #23121 reads in serializable are force to be read only (use JDBC API)
Last trace from client log. Note that after wring read few correct reads are successful. Which means that data might be actually valid.
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information