From 99a4ed387f369ab4d0fc26a94a4ed0878921ac65 Mon Sep 17 00:00:00 2001 From: Agniva De Sarker Date: Tue, 21 Jan 2025 20:12:13 +0530 Subject: [PATCH 01/15] Add policy to bump postgres minimum version --- .../install/prepare-mattermost-database.rst | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 1795b49f502..aa268eee194 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -204,3 +204,39 @@ When the PostgreSQL database is installed, and the initial setup is complete, yo .. important:: If you are upgrading a major version of Postgres, it is essential that ``ANALYZE VERBOSE`` is run on the database post upgrade. This is necessary to re-populate the ``pg_statistics`` table used to generate optimal query plans. The database performance might suffer if this step is not done. + + +### Policy for Updating the Minimum Supported Postgres Version + +#### Overview of the Challenge +Currently, Mattermost does not have a clear, documented policy to determine when to update the minimum supported Postgres version. This lack of clarity creates confusion for both the Mattermost team and its customers. + +Challenges include: +- Limited ability to test Mattermost compatibility with all possible Postgres versions. +- Gaps in testing actively supported Postgres versions, which may compromise software reliability. +- Inability to leverage new Postgres features for better performance and functionality. + +#### Proposed Solution +Mattermost proposes the following policy for updating the minimum supported Postgres version: + +1. **Alignment with Oldest Actively Supported Postgres Version**: + - Mattermost will adopt the oldest Postgres version that is still actively maintained. + +2. **Upgrade Timeline**: + - When a specific Postgres version (e.g., version X) reaches its end of life (EOL), Mattermost will bump the minimum required version after the next **Extended Support Release (ESR)**. + - Example: If version X becomes unsupported before ESR 10.5, the minimum version will update to X+1 in ESR 10.5. + +3. **Customer Buffer Timeline**: + - Since each ESR is supported for 9 months, customers will have a 9-month window to plan, test, and upgrade their Postgres version. + +**Effect of the Policy**: +If this proposal is accepted, Mattermost will require Postgres 13 as the minimum version starting with 10.6. We start with 10.6 to kick off the policy, but going forward, it will be only on ESR releases. + +#### **Frequently Asked Questions (FAQs)** + +1. **What about MySQL?** + MySQL is being deprecated starting with version 11. No further effort is being allocated to MySQL support. + +2. **What if customers cannot upgrade their database in time?** + The policy aims to provide customers with a 9-month preparation period for upgrades. If this timeframe is insufficient, extended ESR support may be discussed on a case-by-case basis. The goal is to improve transparency so customers can align with the announced timelines. + From e10b928310b0422b2e454ab92460d0dbbb3843aa Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Tue, 21 Jan 2025 11:36:06 -0500 Subject: [PATCH 02/15] Wordsmithing, MD > RST, & breadcrumb links --- source/deploy/postgres-migration.rst | 2 +- .../install/prepare-mattermost-database.rst | 43 +++++++------------ .../software-hardware-requirements.rst | 8 ++-- source/install/trouble-postgres.rst | 2 +- 4 files changed, 23 insertions(+), 32 deletions(-) diff --git a/source/deploy/postgres-migration.rst b/source/deploy/postgres-migration.rst index cc2905bcf75..c6833336b17 100644 --- a/source/deploy/postgres-migration.rst +++ b/source/deploy/postgres-migration.rst @@ -4,7 +4,7 @@ Migration guidelines from MySQL to PostgreSQL .. include:: ../_static/badges/allplans-selfhosted.rst :start-after: :nosearch: -From Mattermost v8.0, PostgreSQL is our database of choice for Mattermost to enhance the platform’s performance and capabilities. Recognizing the importance of supporting the community members who are interested in migrating from a MySQL database, we have taken proactive measures to provide guidance and best practices. +From Mattermost v8.0, :ref:`PostgreSQL ` is our database of choice for Mattermost to enhance the platform’s performance and capabilities. Recognizing the importance of supporting the community members who are interested in migrating from a MySQL database, we have taken proactive measures to provide guidance and best practices. .. toctree:: :maxdepth: 1 diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index aa268eee194..ac0e2fb64ca 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -4,12 +4,15 @@ Prepare your Mattermost database .. include:: ../_static/badges/allplans-selfhosted.rst :start-after: :nosearch: -You need a PostgreSQL database. See the :ref:`database software ` documentation for details on database version support, and see the :doc:`Migrate from MySQL to PostgreSQL ` documentation for details on migrating from MySQL to PostgreSQL. +You need a PostgreSQL database. See the :ref:`database software ` and the `minimum supported version policy <#minimum-supported-version-policy>`__ documentation for version support details, and see the :doc:`Migrate from MySQL to PostgreSQL ` documentation to learn more about migrating from MySQL to PostgreSQL. .. tip:: Looking for information on working with a MySQL database? See the :doc:`prepare your Mattermost MySQL database ` documentation for details. +Set up a PostgreSQL database +---------------------------- + To set up a PostgreSQL database for use by the Mattermost server: 1. Log in to the server that will host the database, and install PostgreSQL. See the `PostgreSQL `__ documentation for details. When the installation is complete, the PostgreSQL server is running, and a Linux user account called *postgres* has been created. @@ -206,37 +209,23 @@ When the PostgreSQL database is installed, and the initial setup is complete, yo If you are upgrading a major version of Postgres, it is essential that ``ANALYZE VERBOSE`` is run on the database post upgrade. This is necessary to re-populate the ``pg_statistics`` table used to generate optimal query plans. The database performance might suffer if this step is not done. -### Policy for Updating the Minimum Supported Postgres Version - -#### Overview of the Challenge -Currently, Mattermost does not have a clear, documented policy to determine when to update the minimum supported Postgres version. This lack of clarity creates confusion for both the Mattermost team and its customers. - -Challenges include: -- Limited ability to test Mattermost compatibility with all possible Postgres versions. -- Gaps in testing actively supported Postgres versions, which may compromise software reliability. -- Inability to leverage new Postgres features for better performance and functionality. - -#### Proposed Solution -Mattermost proposes the following policy for updating the minimum supported Postgres version: +Minimum supported version policy +--------------------------------- -1. **Alignment with Oldest Actively Supported Postgres Version**: - - Mattermost will adopt the oldest Postgres version that is still actively maintained. +To make planning easier and ensure your Mattermost deployment remains fast and secure, we are introducing a policy for updating the minimum supported version of Postgres. The oldest supported Postgres version Mattermost supports will match the oldest version supported by the Postgres community. This ensures you benefit from the latest features and security updates. -2. **Upgrade Timeline**: - - When a specific Postgres version (e.g., version X) reaches its end of life (EOL), Mattermost will bump the minimum required version after the next **Extended Support Release (ESR)**. - - Example: If version X becomes unsupported before ESR 10.5, the minimum version will update to X+1 in ESR 10.5. +This policy change takes effect from Mattermost v10.6, where the minimum Postgres version required will be Postgres 13. This aligns with the Postgres community's support policy, which provides 5 years of support for each major version. -3. **Customer Buffer Timeline**: - - Since each ESR is supported for 9 months, customers will have a 9-month window to plan, test, and upgrade their Postgres version. +.. note:: -**Effect of the Policy**: -If this proposal is accepted, Mattermost will require Postgres 13 as the minimum version starting with 10.6. We start with 10.6 to kick off the policy, but going forward, it will be only on ESR releases. + Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. When a Postgres version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. -#### **Frequently Asked Questions (FAQs)** +Customers will have 9 months to plan, test, and upgrade their Postgres version before the new requirement takes effect. If you need more time, extended ESR support may be available on a case-by-case basis. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. -1. **What about MySQL?** - MySQL is being deprecated starting with version 11. No further effort is being allocated to MySQL support. +Frequently asked questions +~~~~~~~~~~~~~~~~~~~~~~~~~~~ -2. **What if customers cannot upgrade their database in time?** - The policy aims to provide customers with a 9-month preparation period for upgrades. If this timeframe is insufficient, extended ESR support may be discussed on a case-by-case basis. The goal is to improve transparency so customers can align with the announced timelines. +What about MySQL databases? +^^^^^^^^^^^^^^^^^^^^^^^^^^^ +Mattermost is :ref:`deprecating support for MySQL ` starting with v11. We aren't actively maintaining or working on MySQL support. \ No newline at end of file diff --git a/source/install/software-hardware-requirements.rst b/source/install/software-hardware-requirements.rst index 8713847511c..4dc2fd5cca4 100644 --- a/source/install/software-hardware-requirements.rst +++ b/source/install/software-hardware-requirements.rst @@ -101,9 +101,11 @@ Database software Amazon Aurora equivalents of both PostgreSQL and MySQL are also supported. -See the :doc:`Migrate from MySQL to PostgreSQL ` product documentation for details on migrating from MySQL to PostgreSQL. +See the :ref:`minimum supported version policy ` documentation for minimum Postgres version support details, and see the :doc:`Migrate from MySQL to PostgreSQL ` product documentation to learn about migrating from MySQL to PostgreSQL. -MariaDB v10+ no longer functions as a MySQL drop-in replacement, and it's not supported for Mattermost due to the requirement of MySQL 5.7.12. Prior versions of MariaDB were not officially supported but may have functioned in older Mattermost releases. If you are running MariaDB now, migrating from MariaDB to the MySQL equivalent is recommended. +.. important:: + + MariaDB v10+ no longer functions as a MySQL drop-in replacement, and it's not supported for Mattermost due to the requirement of MySQL 5.7.12. Prior versions of MariaDB were not officially supported but may have functioned in older Mattermost releases. If you are running MariaDB now, migrating from MariaDB to the MySQL equivalent is recommended. Deployments requiring searching in Chinese, Japanese, and Korean languages require MySQL 5.7.6+ and the configuration of `ngram Full-Text parser `__. For searching two characters, you will also need to set ``ft_min_word_len`` and ``innodb_ft_min_token_size`` to ``2`` and restart MySQL. See `CJK discussion `__ for details. @@ -120,7 +122,7 @@ Search limitations on MySQL: - The migration system requires the MySQL database user to have additional `EXECUTE`, `CREATE ROUTINE`, `ALTER ROUTINE` and `REFERENCES` privileges to run schema migrations. MySQL 8 Support -^^^^^^^^^^^^^^^^ +:::::::::::::::: In MySQL 8.0.4, the default authentication plugin was changed from ``mysql_native_password`` to ``caching_sha2_password``. Therefore, you will need to enable ``mysql_native_password`` by adding the following entry in your MySQL configuration file: diff --git a/source/install/trouble-postgres.rst b/source/install/trouble-postgres.rst index 99514287292..a4ebf3319a4 100644 --- a/source/install/trouble-postgres.rst +++ b/source/install/trouble-postgres.rst @@ -1,7 +1,7 @@ PostgreSQL installation troubleshooting ======================================= -Mattermost supports PostgreSQL v12+. +From Mattermost v8.0, :ref:`PostgreSQL ` is our database of choice for Mattermost to enhance the platform’s performance and capabilities. 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. From c449e5f02e37e7f84c8c0dd692d48fa060e123db Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Wed, 22 Jan 2025 08:32:46 -0500 Subject: [PATCH 03/15] Update source/install/prepare-mattermost-database.rst Co-authored-by: Amy Blais <29708087+amyblais@users.noreply.github.com> --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index ac0e2fb64ca..301eb065042 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -212,7 +212,7 @@ When the PostgreSQL database is installed, and the initial setup is complete, yo Minimum supported version policy --------------------------------- -To make planning easier and ensure your Mattermost deployment remains fast and secure, we are introducing a policy for updating the minimum supported version of Postgres. The oldest supported Postgres version Mattermost supports will match the oldest version supported by the Postgres community. This ensures you benefit from the latest features and security updates. +To make planning easier and ensure your Mattermost deployment remains fast and secure, we are introducing a policy for updating the minimum supported version of PostgreSQL. The oldest supported PostgreSQL version Mattermost supports will match the oldest version supported by the PostgreSQL community. This ensures you benefit from the latest features and security updates. This policy change takes effect from Mattermost v10.6, where the minimum Postgres version required will be Postgres 13. This aligns with the Postgres community's support policy, which provides 5 years of support for each major version. From 27232c0d35c270497b7e37d8db372f722a6a1882 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Wed, 22 Jan 2025 08:32:51 -0500 Subject: [PATCH 04/15] Update source/install/prepare-mattermost-database.rst Co-authored-by: Amy Blais <29708087+amyblais@users.noreply.github.com> --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 301eb065042..bfe1046770f 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -218,7 +218,7 @@ This policy change takes effect from Mattermost v10.6, where the minimum Postgre .. note:: - Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. When a Postgres version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. + Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. Customers will have 9 months to plan, test, and upgrade their Postgres version before the new requirement takes effect. If you need more time, extended ESR support may be available on a case-by-case basis. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. From c8dafd5e25b7caa579249aab8af2d859259da6fa Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Wed, 22 Jan 2025 08:33:23 -0500 Subject: [PATCH 05/15] Update source/install/prepare-mattermost-database.rst Co-authored-by: Amy Blais <29708087+amyblais@users.noreply.github.com> --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index bfe1046770f..2a739b26696 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -214,7 +214,7 @@ Minimum supported version policy To make planning easier and ensure your Mattermost deployment remains fast and secure, we are introducing a policy for updating the minimum supported version of PostgreSQL. The oldest supported PostgreSQL version Mattermost supports will match the oldest version supported by the PostgreSQL community. This ensures you benefit from the latest features and security updates. -This policy change takes effect from Mattermost v10.6, where the minimum Postgres version required will be Postgres 13. This aligns with the Postgres community's support policy, which provides 5 years of support for each major version. +This policy change takes effect from Mattermost v10.6, where the minimum PostgreSQL version required will be PostgreSQL 13. This aligns with the PostgreSQL community's support policy, which provides 5 years of support for each major version. .. note:: From 5a36c0618b3a15765fc3dc9e86a14120eba30e68 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Wed, 22 Jan 2025 08:33:57 -0500 Subject: [PATCH 06/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 2a739b26696..ee6d6f9debe 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -220,7 +220,7 @@ This policy change takes effect from Mattermost v10.6, where the minimum Postgre Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. -Customers will have 9 months to plan, test, and upgrade their Postgres version before the new requirement takes effect. If you need more time, extended ESR support may be available on a case-by-case basis. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. +Customers will have 9 months to plan, test, and upgrade their PostgreSQL version before the new requirement takes effect. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. Frequently asked questions ~~~~~~~~~~~~~~~~~~~~~~~~~~~ From 70eae7711a0b042a3a17200e79fd00f7f1c7a216 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Wed, 22 Jan 2025 08:34:07 -0500 Subject: [PATCH 07/15] Update source/install/software-hardware-requirements.rst Co-authored-by: Amy Blais <29708087+amyblais@users.noreply.github.com> --- source/install/software-hardware-requirements.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/software-hardware-requirements.rst b/source/install/software-hardware-requirements.rst index 4dc2fd5cca4..d371efa3ab6 100644 --- a/source/install/software-hardware-requirements.rst +++ b/source/install/software-hardware-requirements.rst @@ -101,7 +101,7 @@ Database software Amazon Aurora equivalents of both PostgreSQL and MySQL are also supported. -See the :ref:`minimum supported version policy ` documentation for minimum Postgres version support details, and see the :doc:`Migrate from MySQL to PostgreSQL ` product documentation to learn about migrating from MySQL to PostgreSQL. +See the :ref:`minimum supported version policy ` documentation for minimum PostgreSQL version support details, and see the :doc:`Migrate from MySQL to PostgreSQL ` product documentation to learn about migrating from MySQL to PostgreSQL. .. important:: From 20c3ca1e1bc7dadf0797626a4f31116345fa6d88 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Wed, 22 Jan 2025 15:00:28 -0500 Subject: [PATCH 08/15] Incorporated reviewer feedback --- source/install/prepare-mattermost-database.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index ee6d6f9debe..4cf2c9368fe 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -218,7 +218,11 @@ This policy change takes effect from Mattermost v10.6, where the minimum Postgre .. note:: - Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. + - Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. + - When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. This means the following future PostgreSQL minimum version increases as follows: + + - Mattermost will require PostgreSQL 14 from the Mattermost v10.11 ESR scheduled for August 2025. + - Mattermost will require PostgreSQL 15 from the Mattermost v11.5 ESR scheduled for February 2026. Customers will have 9 months to plan, test, and upgrade their PostgreSQL version before the new requirement takes effect. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. From 3c22351252b7e9b8dfe5e26b5d20fe1d104ef999 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Thu, 23 Jan 2025 09:06:59 -0500 Subject: [PATCH 09/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 4cf2c9368fe..bd1505a0c2c 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -222,7 +222,7 @@ This policy change takes effect from Mattermost v10.6, where the minimum Postgre - When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. This means the following future PostgreSQL minimum version increases as follows: - Mattermost will require PostgreSQL 14 from the Mattermost v10.11 ESR scheduled for August 2025. - - Mattermost will require PostgreSQL 15 from the Mattermost v11.5 ESR scheduled for February 2026. + - Mattermost will require PostgreSQL 15 from the Mattermost v11.5 ESR forecasted for February 2026. Customers will have 9 months to plan, test, and upgrade their PostgreSQL version before the new requirement takes effect. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. From 00b7da613c69e7e0d97b0e6b696bebf0dc968225 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Thu, 23 Jan 2025 13:59:26 -0500 Subject: [PATCH 10/15] Incorporated reviewer feedback --- .../install/prepare-mattermost-database.rst | 24 +++++++++++++++---- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index bd1505a0c2c..1bf0724fbd0 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -218,11 +218,25 @@ This policy change takes effect from Mattermost v10.6, where the minimum Postgre .. note:: - - Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. - - When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. This means the following future PostgreSQL minimum version increases as follows: - - - Mattermost will require PostgreSQL 14 from the Mattermost v10.11 ESR scheduled for August 2025. - - Mattermost will require PostgreSQL 15 from the Mattermost v11.5 ESR forecasted for February 2026. + Mattermost v10.6 is not an :ref:`Extended Support Release (ESR) `. Going forward, this database version support policy will only apply to ESR releases. + +When a PostgreSQL version reaches its end of life (EOL), Mattermost will require a newer version starting with the next scheduled ESR release. This means the following future PostgreSQL minimum version increases as follows: + ++-----------------------------------------------------------+------------------+--------------------------------+ +| **Mattermost Version** | **Release Date** | **Minimum PostgreSQL Version** | ++===========================================================+==================+================================+ +| :ref:`v9.11 ESR ` | 2024-8-15 | 11.x | ++-----------------------------------------------------------+------------------+--------------------------------+ +| v10.5 ESR | 2025-2-15 | 11.x | ++-----------------------------------------------------------+------------------+--------------------------------+ +| v10.6 | 2025-3-15 | 13.x | ++-----------------------------------------------------------+------------------+--------------------------------+ +| v10.11 ESR | 2025-7-15 | 13.x | ++-----------------------------------------------------------+------------------+--------------------------------+ +| v11.5 ESR ``*`` | 2026-2-15 | 13.x (EOL 12-11-2026) | ++-----------------------------------------------------------+------------------+--------------------------------+ + +``*`` Forcasted release version and date. Customers will have 9 months to plan, test, and upgrade their PostgreSQL version before the new requirement takes effect. This policy aims to provide clarity and transparency so you can align database upgrades with the Mattermost release schedule. Contact a `Mattermost Expert `_. to discuss your options. From 5872acf0be5fe16259c984474dc4684994ec7304 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Thu, 23 Jan 2025 15:59:38 -0500 Subject: [PATCH 11/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 1bf0724fbd0..5df4ad838c2 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -231,7 +231,7 @@ When a PostgreSQL version reaches its end of life (EOL), Mattermost will require +-----------------------------------------------------------+------------------+--------------------------------+ | v10.6 | 2025-3-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ -| v10.11 ESR | 2025-7-15 | 13.x | +| v10.11 ESR | 2025-8-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ | v11.5 ESR ``*`` | 2026-2-15 | 13.x (EOL 12-11-2026) | +-----------------------------------------------------------+------------------+--------------------------------+ From 8559416a23d754c37f4b98fc39166e7e9a216d62 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Fri, 24 Jan 2025 08:25:06 -0500 Subject: [PATCH 12/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 5df4ad838c2..b7e90a29b05 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -231,7 +231,7 @@ When a PostgreSQL version reaches its end of life (EOL), Mattermost will require +-----------------------------------------------------------+------------------+--------------------------------+ | v10.6 | 2025-3-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ -| v10.11 ESR | 2025-8-15 | 13.x | +| v10.11 ESR | 2025-8-15 | 14.x | +-----------------------------------------------------------+------------------+--------------------------------+ | v11.5 ESR ``*`` | 2026-2-15 | 13.x (EOL 12-11-2026) | +-----------------------------------------------------------+------------------+--------------------------------+ From 6b185a90957e35813f44653acd327a24c315dfe2 Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Fri, 24 Jan 2025 08:26:21 -0500 Subject: [PATCH 13/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index b7e90a29b05..5df4ad838c2 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -231,7 +231,7 @@ When a PostgreSQL version reaches its end of life (EOL), Mattermost will require +-----------------------------------------------------------+------------------+--------------------------------+ | v10.6 | 2025-3-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ -| v10.11 ESR | 2025-8-15 | 14.x | +| v10.11 ESR | 2025-8-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ | v11.5 ESR ``*`` | 2026-2-15 | 13.x (EOL 12-11-2026) | +-----------------------------------------------------------+------------------+--------------------------------+ From ce70c538c899d7ef2240cc38df0871125ad2a3ec Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Fri, 24 Jan 2025 08:28:15 -0500 Subject: [PATCH 14/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 5df4ad838c2..12f12fff05f 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -233,7 +233,7 @@ When a PostgreSQL version reaches its end of life (EOL), Mattermost will require +-----------------------------------------------------------+------------------+--------------------------------+ | v10.11 ESR | 2025-8-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ -| v11.5 ESR ``*`` | 2026-2-15 | 13.x (EOL 12-11-2026) | +| v11.5 ESR ``*`` | 2026-2-15 | 14.x (EOL 2025-11-13) | +-----------------------------------------------------------+------------------+--------------------------------+ ``*`` Forcasted release version and date. From 856079a446ca91b36dbf2fce0335227eb1b7f96f Mon Sep 17 00:00:00 2001 From: "Carrie Warner (Mattermost)" <74422101+cwarnermm@users.noreply.github.com> Date: Mon, 27 Jan 2025 08:52:09 -0500 Subject: [PATCH 15/15] Update source/install/prepare-mattermost-database.rst --- source/install/prepare-mattermost-database.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/install/prepare-mattermost-database.rst b/source/install/prepare-mattermost-database.rst index 12f12fff05f..10d66909d0e 100644 --- a/source/install/prepare-mattermost-database.rst +++ b/source/install/prepare-mattermost-database.rst @@ -233,7 +233,7 @@ When a PostgreSQL version reaches its end of life (EOL), Mattermost will require +-----------------------------------------------------------+------------------+--------------------------------+ | v10.11 ESR | 2025-8-15 | 13.x | +-----------------------------------------------------------+------------------+--------------------------------+ -| v11.5 ESR ``*`` | 2026-2-15 | 14.x (EOL 2025-11-13) | +| v11.5 ESR ``*`` | 2026-2-15 | 14.x (EOL 2026-11-12) | +-----------------------------------------------------------+------------------+--------------------------------+ ``*`` Forcasted release version and date.