From a7b9e67c06c659f77304af6d0016cbc7f8693fd9 Mon Sep 17 00:00:00 2001 From: Alex Vandiver Date: Tue, 11 Jul 2023 21:24:12 +0000 Subject: [PATCH] docs: Mention the PostgreSQL upgrade in the release upgrade section. Users can, quite understandably, assume that upgrading Zulip upgraded the underlying PostgreSQL version. Though it is mentioned at the top of the page, mentioning it here clarifies that it is an additional step. --- docs/production/upgrade.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/production/upgrade.md b/docs/production/upgrade.md index 686a567bfc..8337d0f5d8 100644 --- a/docs/production/upgrade.md +++ b/docs/production/upgrade.md @@ -64,6 +64,9 @@ doing the final upgrade at off hours, or buying a support contract. See the [troubleshooting guide](#troubleshooting-and-rollback) if you run into any issues or need to roll back the upgrade. +After you have completed the Zulip upgrade, you may also wish to [upgrade the +version of PostgreSQL][#upgrading-postgresql]. + ## Upgrading from a Git repository Zulip supports upgrading a production installation to any commit in a