From 8e73ea1f6f49898104d3bd47eac9ee143ad49d05 Mon Sep 17 00:00:00 2001 From: Philip O'Toole Date: Mon, 7 Aug 2023 18:09:52 -0400 Subject: [PATCH] CHANGELOG --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 67b321a2..4ed3727a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,7 +6,7 @@ Release 8.0.0 is in active development, with the goal of supporting much larger When officially released 8.0 will support (mostly) seamless upgrades from the 7.x series. However until the official release you must follow these steps to upgrade from 7.x: - Backup your data and load it into a new 8.0 system. -- 8.0 always runs with an on-disk database, in-memory databases are no longer supported. If you were previously running in in-memory mode (the default), you don't need to do anything. But if you were previously passing `-on-disk` to `rqlited` so that rqlite ran in on-disk mode, you must now remove that flag. +- 8.0 always runs with an on-disk database, in-memory databases are no longer supported. Improvements made late in the 7.0 series means there is little difference in write performance between in-memory and on-disk modes, and supporting both modes just means confusion and higher development costs. If you were previously running in in-memory mode (the default), you don't need to do anything. But if you were previously passing `-on-disk` to `rqlited` so that rqlite ran in on-disk mode, you must now remove that flag. ### Implementation changes and bug fixes - [PR #1337](https://github.com/rqlite/rqlite/pull/1337): Store can now load from an io.Reader.