Commit-time block checking limited to blocks in RAM
Details
| Detail name | Value |
|---|---|
| Changelog Number | 27895 |
| Type | Improvement |
| Status | Resolved |
| Fix Versions | Exasol 2025.2.0, Exasol 2025.1.9 |
| Resolution Date | 2025-12-17 |
Background
Normal database operation includes validity checking of data blocks during a commit. This ensures the blocks are written without corruption and is performed out of an abundance of caution. By default, this validity check included blocks written to memory as well as those swapped to disk or an object-storage backend.
Improvement
As there have been no cases among Exasol users of invalid blocks in more than a year, the default behavior will be relaxed such that there is no longer validity checking of blocks that are not resident in memory. This means that blocks on disk or in object storage are not validity checked. This can result in noticeable performance improvements.
Validity checking of in-memory blocks does not have a significant performance impact, and therefore remains in effect.
