Merge branch 'master' into v10.9-documentation

Author: amyblais

source/deploy/postgres-migration.rst

@@ -156,6 +156,28 @@ You can check for the default ``search_path`` by running the following command:
 
   SELECT boot_val FROM pg_settings WHERE name='search_path';
 
+Permission issues when accessing the schema in PostgreSQL
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you run into a permission issue during step 2 where the command reports a permission issue similar to the following:
+
+.. code-block:: text
+
+   An Error Occurred: could not check schema owner: the user “mmuser” is not owner of the “public” schema
+
+Ensure that the ``mmuser`` user in PostgreSQL is the owner of the schema.
+
+1. Connect to PostgreSQL using ``sudo -u postgres psql``.
+2. Select the ``mattermost`` database using ``\c mattermost``. Verify you are using the right database by running ``SELECT current_database();``. The command should output ``mattermost``.
+3. Run the following commands:
+
+   .. code-block:: sql
+
+      ALTER SCHEMA public OWNER TO mmuser;
+      GRANT ALL ON SCHEMA public TO mmuser;
+
+Then, re-run the command from step 2.
+
 Contact Support
 ---------------
 

source/deploy/server/preparations.rst

@@ -80,7 +80,7 @@ PostgreSQL v13+ is required for Mattermost server installations. :doc:`MySQL dat
       .. code-block:: sql
 
          ALTER DATABASE mattermost OWNER TO mmuser;
-         GRANT USAGE, CREATE ON SCHEMA PUBLIC TO mmuser;
+         GRANT USAGE, CREATE ON SCHEMA public TO mmuser;
 
 3. Configure PostgreSQL for remote connections (if database is on a separate server):
 

source/deploy/server/trouble-postgres.rst

@@ -5,10 +5,10 @@ From Mattermost v8.0, :ref:`PostgreSQL <deploy/software-hardware-requirements:da
 
 PostgreSQL v15 introduces changes that may affect compatibility with previous releases. If you're deploying a fresh installation of PostgreSQL v15, run this command: ``GRANT CREATE ON SCHEMA public TO PUBLIC`` to ensure that you can use Mattermost.
 
-PostgresSQL full-text search fails to use indexes with non-english ``default_text_search_config``
+PostgreSQL full-text search fails to use indexes with non-English ``default_text_search_config``
 --------------------------------------------------------------------------------------------------
 
-Mattermost uses ``default_text_search_config`` for full-text search in PostgresSQL databases, as opposed to a hardcoded text search config. However, indexes are still created with a hardcoded text search config (english) and as a result, full-text search may never use the indexes.
+Mattermost uses ``default_text_search_config`` for full-text search in PostgreSQL databases, as opposed to a hardcoded text search config. However, indexes are still created with a hardcoded text search config (english) and as a result, full-text search may never use the indexes.
 
 Some of the tables in Mattermost, like ``Posts`` or ``Users``, contain GIN indexes to improve the database full-text search feature in PostgreSQL.