@harperfast/rocksdb-js 2.9.0 → 2.9.1

package/README.md

@@ -95,10 +95,20 @@ Creates a new database instance.
   - `maxWriteBufferSizeToMaintain: number` The number of bytes of recent memtable history to keep in
     memory for transaction conflict checking. `-1` (the default) derives the value from
     `maxWriteBufferNumber * writeBufferSize` (the RocksDB-recommended default for optimistic
-    transactions) — except when a stalling [`writeBufferManager`](#dbconfigoptions) is configured
-    (`writeBufferManagerSize > 0` with `writeBufferManagerAllowStall`), in which case it resolves to
-    `0` to avoid retaining memtable history the manager will never release. An explicit non-negative
-    value is always honored as-is.
+    transactions) — except when the database has a [`writeBufferManager`](#dbconfigoptions)
+    attached, in which case it resolves to `1` so the manager is not filled with history it will
+    never release. What decides this is the manager the database itself holds, not the current
+    `writeBufferManagerSize`: a column family created later on an already-open database is clamped
+    too, because its history is still charged to that manager. It also applies to any attached
+    manager, not only a stalling one — `writeBufferManagerAllowStall` can be changed at runtime
+    while this value is fixed when a column family is created, and history the budget cannot reclaim
+    is a problem either way. `1` is the smallest target a transactional database can be given: RocksDB's transaction wrappers rewrite a `0` target to
+    the derived value, so `0` requests the _largest_ history rather than none, and an explicitly
+    requested `0` is normalized to `1` for the same reason. A positive target still retains the most
+    recent flushed memtable per column family until that family's next write. An explicit positive
+    value is honored as-is; sizing it against the budget and the column-family count is then yours,
+    and a configuration whose known families already reach the budget is reported on the
+    [`'log.warn'`](#event-api) channel.
   - `name: string` The column family name. Defaults to `"default"`.
   - `noBlockCache: boolean` When `true`, disables the block cache. Block caching is enabled by
     default and the cache is shared across all database instances.
@@ -236,8 +246,10 @@ Sets global database settings.
     back into the reclaimed space. Defaults to `false`.
   - `writeBufferManagerSize: number` Total memtable memory limit (bytes) shared across every
     database opened in this process. When set, RocksDB uses a single `WriteBufferManager` so write
-    buffers are bounded process-wide rather than per database. A value of `0` disables the manager.
-    Defaults to `0`.
+    buffers are bounded process-wide rather than per database. Defaults to `0`, which means no
+    manager. Setting `0` later stops _new_ opens from attaching one, but does not detach or resize
+    the manager a database already holds — `write_buffer_manager` is fixed for the life of an open
+    database, so its memtables stay charged against that budget.
 
 ```typescript
 RocksDatabase.config({
@@ -1148,8 +1160,8 @@ uses this timestamp as the batch key; producers may also encode it into their ow
 
 Type: `number`
 
-The transaction ID represented as a 32-bit unsigned integer. Transaction IDs are unique to the
-RocksDB database path, regardless the database name/column family.
+The transaction ID, a positive integer no greater than `Number.MAX_SAFE_INTEGER`. Transaction IDs
+are unique to the RocksDB database path, regardless the database name/column family.
 
 #### `txn.setTimestamp(ts?: number): void`
 

package/dist/index.cjs

@@ -1293,7 +1293,15 @@ var DBIterator = class {
 			this.iterator.return?.();
 			return DONE_RESULT;
 		}
-		const result = this.iterator.next();
+		let result;
+		try {
+			result = this.iterator.next();
+		} catch (err) {
+			try {
+				this.iterator.return?.();
+			} catch {}
+			throw err;
+		}
 		if (result === ITERATOR_RESULT_DONE) return DONE_RESULT;
 		this.#yielded++;
 		const includeValues = this.#includeValues;
@@ -1571,10 +1579,16 @@ var Store = class {
 	/**
 	* The bytes of recent memtable history to retain in memory for transaction
 	* conflict checking. `-1` derives the value from
-	* `maxWriteBufferNumber * writeBufferSize`, except under a stalling
-	* `writeBufferManager`, where it derives `0`: retained history is charged to
-	* that manager and is only trimmable down to this target, so a target the
-	* budget cannot hold stalls writes permanently. Set a number to size it
+	* `maxWriteBufferNumber * writeBufferSize`, except when a
+	* `writeBufferManager` is configured, where it derives `1`: retained history
+	* is charged to that manager and is only trimmable down to this target, so a
+	* target the budget cannot hold is memory the manager never reclaims, and
+	* stalls writes permanently when `writeBufferManagerAllowStall` is on. Any
+	* configured manager, not only a stalling one — that flag is mutable at
+	* runtime while this value is fixed when the family is created. `1`, not `0`, because
+	* RocksDB's transaction wrappers rewrite a `0` target to the derived value —
+	* so `0` asks for the largest history rather than none, and an explicit `0`
+	* is normalized to `1` for that reason. Set a positive number to size it
 	* yourself against the budget and the column-family count.
 	*/
 	maxWriteBufferSizeToMaintain;
@@ -3789,7 +3803,7 @@ function loadLastPosition(transactionLog, readUncommitted) {
 //#region src/index.ts
 const versions = {
 	rocksdb: version,
-	"rocksdb-js": "2.9.0"
+	"rocksdb-js": "2.9.1"
 };
 
 //#endregion