Release notes
Release v1.10.1 mistakenly did not update ORIOLEDB_VERSION. This release fixes it by setting new correct version to ORIOLEDB_VERSION.
Extension SQL version stays at 1.10. No storage or WAL format changes.
Query correctness:
- A row lock conflict walk now stops at the transaction's own latest version (82b7815)
- Another transaction's in-progress version, or a lock-only record, is no longer taken as the row's final version (8d96cec, c6161b6)
- UPDATEs running during a concurrent index build are now captured correctly (be8ad80)
Crashes and stability:
- The background writer no longer crashes on indexes with range, array or composite keys (a0311c3)
- Structure and index functions now handle NULL arguments (b592d53)
- Fixed a memory leak in CREATE INDEX on an expression over TOASTed rows (709be8c)
Recovery/replication:
- Moving a database to another tablespace on a physical standby now works correctly (73c99ad)
Configuration and diagnostics:
- Fixed the default value of
orioledb.rewind_max_transactions(ba092c6) - Checkpoint page IO error messages now show the correct file names (c85ddd8)
Full Changelog: v1.10.1...v1.10.2