Unexpected transaction conflict when creating and dropping objects
Details
| Detail name | Value |
|---|---|
| Changelog Number | 7985 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0, Exasol 6.1.0, Exasol 6.2.beta1 |
| Fix Versions | Exasol 6.1.x |
| Resolution Date | 2023-03-28 |
Description
Under extremely rare circumstances yet to be determined, it is possible to get unexpected transaction collisions and subsequent rollbacks.
For two transactions T1 and T2, the conditions for this to happen are as follows:
- Transaction T1 creates and then drops table MYSCHEMA.T
- Transaction T2 creates and then drops table MYSCHEMA.T (same schema, same table name)
- Both transactions commit at the same time
When the above conditions are met a rollback happen extremely seldom (we've seen one occurence in years).
Expected Behavior
Under normal circumstances both transactions finish without conflicts, as they are operating on different objects.
