From 84eb71f72f6bf597bbcee0f4f7c9fa81d5c01a1a Mon Sep 17 00:00:00 2001 From: Shivaram Lingamneni Date: Tue, 7 Jul 2026 22:10:04 -0700 Subject: [PATCH] fix #2399 (#2419) --- default.yaml | 6 +++--- traditional.yaml | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/default.yaml b/default.yaml index d2085379..ea1e5029 100644 --- a/default.yaml +++ b/default.yaml @@ -1117,9 +1117,9 @@ history: # users to query history after disconnections. grace-period: 1h - # options to store history messages in a persistent database (currently only MySQL). - # in order to enable any of this functionality, you must configure a MySQL server - # in the `datastore.mysql` section. enabling persistence overrides the history + # options to store history messages in a persistent database (MySQL, PostgreSQL + # or SQLite). in order to enable any of this functionality, you must configure + # one of those databases above. enabling persistence overrides the history # size limits above (`channel-length`, `client-length`, etc.); persistent # history has no limits other than those imposed by expire-time. persistent: diff --git a/traditional.yaml b/traditional.yaml index ef1e6b72..8b9c396d 100644 --- a/traditional.yaml +++ b/traditional.yaml @@ -1088,9 +1088,9 @@ history: # users to query history after disconnections. grace-period: 1h - # options to store history messages in a persistent database (currently only MySQL). - # in order to enable any of this functionality, you must configure a MySQL server - # in the `datastore.mysql` section. enabling persistence overrides the history + # options to store history messages in a persistent database (MySQL, PostgreSQL + # or SQLite). in order to enable any of this functionality, you must configure + # one of those databases above. enabling persistence overrides the history # size limits above (`channel-length`, `client-length`, etc.); persistent # history has no limits other than those imposed by expire-time. persistent: