Historical reads
Historical queries require a server configuration that explicitly supports them. Ordinary durability and transaction isolation do not imply that older versions are queryable.
Before using historical queries
Section titled “Before using historical queries”Check the installed server’s start --help for time-travel options. Verify retention, timestamp format, schema-change behavior and persistence across restarts using your release.
A historical query must fail clearly when the requested history is unavailable. Do not treat an empty result as proof that no records existed at that time.
Alternatives
Section titled “Alternatives”For application audit history, maintain explicit event or change records with stable identifiers and timestamps. Keep that design separate from the database’s crash-recovery mechanism.
Transactions · Durability · Feature availability
Related
Section titled “Related”This site uses Google Analytics cookies to count visits. Privacy · License