@harperfast/rocksdb-js 2.9.0 → 2.9.1

package/dist/index.d.cts

@@ -551,10 +551,16 @@ export declare class Store {
   /**
    * 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?: number;

package/dist/index.d.mts

@@ -551,10 +551,16 @@ export declare class Store {
   /**
    * 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?: number;

package/dist/index.mjs

@@ -1268,7 +1268,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;
@@ -1546,10 +1554,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;
@@ -3764,7 +3778,7 @@ function loadLastPosition(transactionLog, readUncommitted) {
 //#region src/index.ts
 const versions = {
 	rocksdb: version,
-	"rocksdb-js": "2.9.0"
+	"rocksdb-js": "2.9.1"
 };
 
 //#endregion