Kuzu V0 136 Fixed [TRUSTED]

The vertex scan routine was rewritten to correctly acknowledge the local transaction state, preserving strict serializable ACID transactions. 4. Corrupted Write-Ahead Log (WAL) Recovery

Run:

For the curious engineer, here is the distilled diff that defines the fix:

The release is not just a patch; it is a re-foundation. The three critical memory and concurrency bugs have been eradicated, performance has exceeded pre-regression levels, and the upgrade path is smooth for the vast majority of users. For any team currently stuck on v0.134 or suffering through v0.135, this update is mandatory. kuzu v0 136 fixed

The source code has found a new home through open-source developers who have forked and updated the project under the moniker LadybugDB. Developers seeking to deploy this embedded graph database technology can safely build upon the v0.11.3 framework, confident that the core data integrity, memory leaks, and concurrency bugs have been thoroughly addressed.

Assuming you've installed Kuzu v0.136 (or any version), here's a general guide on getting started:

Here is how to migrate your project:

If you are a current user or evaluating Kùzu for your next AI, recommendation, or knowledge graph project, understanding the enhancements is crucial for optimizing your workflow. What is Kùzu?

Enhancements were made to the query planner to better optimize queries involving multiple OPTIONAL MATCH clauses or complex pattern matching.

Choose one:

The v0.13.6 updates apply rigorous sizing logic to hash slots within the AggregateHashTable structures. This prevents memory leaks and out-of-bounds pointer adjustments when data spills from memory cache over to disk storage. The Future of Graph Databases (w/ The Founder of KuzuDB)

All users on earlier v0.136 are strongly advised to upgrade. No changes to the public API or on-disk format – drop-in replacement.

The final stable release branch tackled critical underlying bugs in memory usage, data ingestion, and transaction states, ensuring the engine remains production-ready for decentralized or serverless architectures. Key Technical Fixes and Infrastructure Upgrades The vertex scan routine was rewritten to correctly