rust and tidesql reference touch ups

Author: guycipher

src/content/docs/reference/rust.md

@@ -40,7 +40,7 @@ The easiest way to add TidesDB to your project is via [crates.io](https://crates
 
 ```toml
 [dependencies]
-tidesdb = "0.7"
+tidesdb = "0.11"
 ```
 
 Or using `cargo add`:
@@ -61,26 +61,31 @@ The build script (`build.rs`) handles linking automatically:
 
 ### Version Selection
 
-Each crate release defaults to a specific TidesDB C library version. You can select a different version using Cargo features:
+Each crate release pins the TidesDB C library version it builds against via a Cargo feature. `tidesdb` 0.11 ships and defaults to **`v9_3_6`** (TidesDB v9.3.6):
 
 ```toml
 [dependencies]
-# Uses the default version (currently v9.2.0)
-tidesdb = "0.8"
+# Uses the default version (v9.3.6)
+tidesdb = "0.11"
+```
+
+A version feature maps directly to the TidesDB C library release tag (e.g., `v9_3_6` → `v9.3.6`). Additional versions are published over time; when more than one is available you can pin a specific one with `default-features = false`:
 
-# Pin to a specific TidesDB version
-tidesdb = { version = "0.8", default-features = false, features = ["v9_0_5"] }
+```toml
+[dependencies]
+# Pin to a specific TidesDB version (once that feature is offered)
+tidesdb = { version = "0.11", default-features = false, features = ["v9_3_6"] }
 ```
 
-Only one version feature should be enabled at a time. The version feature (e.g., `v9_2_0`) maps directly to the TidesDB C library release tag (e.g., `v9.2.0`); when multiple are enabled (such as via dependency unification), the highest version is selected.
+Only one version feature should be enabled at a time; when several are enabled (e.g. via dependency unification), the highest version is selected.
 
 ### Object Store Support
 
 To enable S3 object store support, enable the `objectstore` feature:
 
 ```toml
 [dependencies]
-tidesdb = { version = "0.7", features = ["objectstore"] }
+tidesdb = { version = "0.11", features = ["objectstore"] }
 ```
 
 This requires additional dependencies:
@@ -386,7 +391,7 @@ Between any two single-deletes on the same key, and between the start of the key
 
 This is the right choice for workloads that insert each key exactly once and then delete it exactly once (classic insert-benchmark patterns, secondary-index entries on columns that are never updated, log-style tables with scheduled purges). It is **not** safe for tables that issue repeated updates to the same key. When in doubt, prefer `Transaction::delete`.
 
-Requires tidesdb >= 9.1.0 (the `v9_1_0` Cargo feature, enabled by default in `tidesdb` 0.7).
+Requires tidesdb >= 9.1.0; the default `v9_3_6` build satisfies this.
 
 ```rust
 use tidesdb::{TidesDB, Config, ColumnFamilyConfig};
@@ -768,7 +773,7 @@ fn main() -> tidesdb::Result<()> {
 | `compaction_count` | `u64` | Compaction output SSTables produced by this CF |
 
 :::note[Write-amplification counters]
-The `wal_bytes_written`, `flush_bytes_written`, `compaction_bytes_written`, `compaction_bytes_read`, `user_bytes_written`, `flush_count`, and `compaction_count` fields require tidesdb >= 9.3.4 (the `v9_3_4` Cargo feature or later, enabled by default). On older libraries they are reported as `0`. This CF's write amplification is `(wal_bytes_written + flush_bytes_written + compaction_bytes_written) / user_bytes_written`. In unified-memtable mode `wal_bytes_written` is `0` here — the shared WAL volume is reported db-wide as `DbStats::uwal_bytes_written`.
+The `wal_bytes_written`, `flush_bytes_written`, `compaction_bytes_written`, `compaction_bytes_read`, `user_bytes_written`, `flush_count`, and `compaction_count` fields require tidesdb >= 9.3.4; the default `v9_3_6` build includes them. On older libraries (e.g. an older system library found via pkg-config) they are reported as `0`. This CF's write amplification is `(wal_bytes_written + flush_bytes_written + compaction_bytes_written) / user_bytes_written`. In unified-memtable mode `wal_bytes_written` is `0` here — the shared WAL volume is reported db-wide as `DbStats::uwal_bytes_written`.
 :::
 
 ### Getting Cache Statistics

src/content/docs/reference/tidesql.md

@@ -422,7 +422,7 @@ The primary row CF is different. `UPDATE t SET non_pk_col = ...` writes a fresh
 Primary-CF single-delete is therefore behind the session variable `tidesdb_single_delete_primary`, default OFF. Enabling it is the caller's explicit promise that:
 
 - The session performs no `UPDATE` on non-PK columns of TidesDB tables.
-- The session performs no `REPLACE INTO` or `INSERT ... ON DUPLICATE KEY UPDATE` that hits the line-5143 silent-overwrite path on a table without secondary indexes.
+- The session performs no `REPLACE INTO` or `INSERT ... ON DUPLICATE KEY UPDATE` that hits the silent-overwrite path on a table without secondary indexes.
 - New rows with a given PK are always preceded by a `DELETE` of that PK (append-only or insert-then-delete).
 
 Enable it only when the workload is known to fit this shape. Typical safe cases:
@@ -1224,7 +1224,8 @@ SHOW GLOBAL STATUS LIKE 'tidesdb%';
 | Variable | Description |
 |----------|-------------|
 | `Tidesdb_version` | TideSQL plugin version string (e.g. `4.5.5`) |
-| `Tidesdb_version_hex` | TideSQL plugin version as integer (e.g. `263941` = `0x40505`) |
+| `Tidesdb_version_hex` | TideSQL plugin version as integer (e.g. `263429` = `0x40505`) |
+| `Tidesdb_library_version` | Underlying TidesDB storage library (`libtidesdb`) version string |
 | `Tidesdb_column_families` | Number of active column families |
 | `Tidesdb_global_sequence` | Global MVCC sequence number |
 | `Tidesdb_memtable_bytes` | Total memtable memory usage in bytes |
@@ -1391,7 +1392,7 @@ The engine exposes several system variables that control TidesDB's runtime behav
 | `tidesdb_unified_memtable_skip_list_probability` | 0.0 | Skip-list level promotion probability for the unified memtable; 0.0 keeps the library default |
 | `tidesdb_replica_mode` | OFF | Enable read-only replica mode (writes return SQL error) |
 | `tidesdb_replica_sync_interval` | 5000000 | MANIFEST poll interval for replica sync in microseconds |
-| `tidesdb_fast_shutdown` | OFF | When ON, deinit calls `tidesdb_cancel_background_work` before `tidesdb_close` so in-flight compactions bail at their next checkpoint and shutdown returns quickly. Default OFF lets `tidesdb_close` drain naturally, which is the safer setting for object-store and replica deployments where a mid-compaction cancel can leave S3 with referenced-but-not-yet-uploaded SSTables that confuse a syncing replica |
+| `tidesdb_finish_compactions_on_close` | OFF | Maps to `tidesdb_config_t.finish_compactions_on_close`, applied at open. Default OFF (the library default) makes `tidesdb_close` cancel in-flight compactions at their next checkpoint for a fast shutdown; the cancelled merge discards its uncommitted output and leaves inputs intact, so no data is lost and recovery handles a mid-merge state the same way. Set ON to let in-flight compactions run to completion before close returns, which is the safer setting for object-store and replica deployments where a mid-compaction cancel can leave S3 with referenced-but-not-yet-uploaded SSTables that confuse a syncing replica |
 
 ### Global Variables (dynamic)
 
@@ -1750,7 +1751,7 @@ Multi-statement transactions at `REPEATABLE_READ` or higher isolation may fail a
 | 12.3.1          | >= 4.2.6     | ✔     |
 | 13.0.2          | >= 4.5.4     | ✔     |
 
-Current TideSQL release is 4.5.4 (hex `0x40504`).
+Current TideSQL release is 4.5.5 (hex `0x40505`).
 
 *As versions are tested and confirmed working we update this table. Full Support means the system is tested against all known functionality.*