From 10f7f2047b6e8363c946a641ffc532d1dc73f069 Mon Sep 17 00:00:00 2001 From: August Date: Thu, 25 Apr 2024 15:28:08 +0800 Subject: [PATCH] feat: add faq for uppercase database name when using PostgreSQL meta backend (#76) --- docs/FAQ.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/FAQ.md b/docs/FAQ.md index f2fe6fc..e0cd3e7 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -37,3 +37,7 @@ If the meta store and state store backends that RisingWave is using are all pers persistent), simply delete the RisingWave pods and let them restart to get a full restart of the cluster. Note that `SQLite` meta store and `Local File System` state store are not persistent unless the data paths are in a persistent volume. Please refer to [the installation guide](CONFIGURATION.md) for more details. + +### What to do if risingwave fails to start with PostgreSQL meta backend giving an uppercase database name? + +When starting RisingWave with PostgreSQL as the metadata backend, if the startup fails and you provided an uppercase database name, please ensure that the corresponding uppercase database has been created properly. In PostgreSQL, if you create a database with an uppercase name without using double quotes, the database name will be converted to lowercase. Check [SQL-SYNTAX-IDENTIFIERS](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS) for more details.