blob: 62b271099b2808fc111ff9f44b6890bb553a6ed4 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
From a6cb3533db77ebeb6b7ed86fb3d3dd86c046f4a4 Mon Sep 17 00:00:00 2001
From: Strac Consulting Engineers Pty Ltd <preminik@preminik.com>
Date: Tue, 20 May 2025 23:31:05 +1000
Subject: [PATCH 20/34] Update postgres.md (#18445)
---
changelog.d/18445.doc | 1 +
docs/postgres.md | 8 ++++++++
2 files changed, 9 insertions(+)
create mode 100644 changelog.d/18445.doc
diff --git a/changelog.d/18445.doc b/changelog.d/18445.doc
new file mode 100644
index 0000000000..1e05a791b2
--- /dev/null
+++ b/changelog.d/18445.doc
@@ -0,0 +1 @@
+Add advice for upgrading between major PostgreSQL versions to the database documentation.
diff --git a/docs/postgres.md b/docs/postgres.md
index 51670667e8..d51f54c722 100644
--- a/docs/postgres.md
+++ b/docs/postgres.md
@@ -100,6 +100,14 @@ database:
keepalives_count: 3
```
+## Postgresql major version upgrades
+
+Postgres uses separate directories for database locations between major versions (typically `/var/lib/postgresql/<version>/main`).
+
+Therefore, it is recommended to stop Synapse and other services (MAS, etc) before upgrading Postgres major versions.
+
+It is also strongly recommended to [back up](./usage/administration/backups.md#database) your database beforehand to ensure no data loss arising from a failed upgrade.
+
## Backups
Don't forget to [back up](./usage/administration/backups.md#database) your database!
--
2.49.0
|
