Skip to content

v2.0.1

Release Date: 2026-09-14

Overview

AkasicDB v2.0.1 is a patch release that adds a management function for updating internal components and changes the vector engine's WAL resource manager ID.

Key Changes

  • Added the akasicdb_admin.update() management function. It updates internal components to match the installed AkasicDB release and is included in both fresh installations and database updates.
  • Updated the internal vector engine, VectorOn, to 2.0.1 and changed its custom WAL resource manager ID from 128 to the registered ID 160.
  • GraphOn and TextOn both remain at version 2.0.0.

Updating

The supported update path for this release is the official v2.0.0 → v2.0.1 path.

Shut down the existing server cleanly, install the complete AkasicDB v2.0.1 distribution for the same PostgreSQL major version and edition, and restart the server. Using an account with administrative privileges, run the following two commands in order in each database containing AkasicDB.

ALTER EXTENSION akasicdb UPDATE;
SELECT akasicdb_admin.update();

The first command updates the AkasicDB version and installs the management function. The second updates the internal VectorOn component. Replacing distribution files or a Docker image alone does not change extension versions in existing databases.

For database-specific steps and completion checks, see Updating AkasicDB.

Compatibility and Notes

Existing data, indexes, and privileges are preserved. The vector engine's SQL objects and index storage format remain unchanged. This patch does not require REINDEX.

Updating from v2.0.0 to a later patch version

When updating from v2.0.0 to a later patch version, the vector engine's WAL resource manager ID changes from 128 to 160. PostgreSQL must be shut down cleanly using the existing binaries before installing the new distribution.

Historical WAL written by v2.0.0 is not converted automatically. Crash recovery requiring replay of WAL with ID 128, physical replication and PITR transitions, and downgrading to older binaries are outside the scope of this update procedure.