From d10efe6acb2631a7b7715977e53048dfb80a97de Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Fri, 24 Aug 2018 14:38:15 -0700 Subject: [PATCH] =?UTF-8?q?SQLite=20page=20size=20fix:=20arises=E2=86=92oc?= =?UTF-8?q?curs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../fix-sqlite-tx-db-page-size-issue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/manage-the-rippled-server/fix-sqlite-tx-db-page-size-issue.md b/content/tutorials/manage-the-rippled-server/fix-sqlite-tx-db-page-size-issue.md index fca42cdf3c..899ec310b9 100644 --- a/content/tutorials/manage-the-rippled-server/fix-sqlite-tx-db-page-size-issue.md +++ b/content/tutorials/manage-the-rippled-server/fix-sqlite-tx-db-page-size-issue.md @@ -2,7 +2,7 @@ `rippled` servers with full transaction history (or a very large amount of transaction history) and a database that was initially created with a `rippled` version earlier than 0.40.0 (released January 2017) may encounter a problem with their SQLite database page size that stops the server from operating properly. Servers that store only recent transaction history (the default configuration) and servers whose database files were created with `rippled` version 0.40.0 and later are not likely to encounter this problem. -This document describes steps to detect and correct this problem if it arises. +This document describes steps to detect and correct this problem if it occurs. ## Background