Changeset 7f6bf79b for server/databases/upgradedb.xml

Timestamp:

12/04/2021 12:20:27 PM (2 years ago)

Author:

Thomas Trepl (Moody) <thomas@…>

Branches:

11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

8986fa9

Parents:

bcdfc53

Message:

Textual changes

File:

• server/databases/upgradedb.xml (modified) (3 diffs)

server/databases/upgradedb.xml

@@ -13 +13 @@
   </sect1info>
 
-  <title>Notes on Database Server Software</title>
+  <title>Important notes about upgrading Database Server Software</title>
+
+    <para>Lets start this chapter a bit dramatic with a screenshot
+    of an issue that really happened. Don't be scared if you read
+    this the first time, this issue will not occur if you are going
+    to install the software the first time:</para>
 
 <screen>$ sudo systemctl status postgresql
@@ -39 +44 @@
   </para>
   <para>
-    Even if you are installing a DBMS the initial time, read it
-    anyway, it might give you a guideline on how to set up backup
+    The root cause of the issue shown above was an upgrade
+    of the server software to a newer major version but letting the
+    data files untouched. The admin was able to recover without any
+    loss of data.
+  </para>
+  <para>
+    Even if you are installing a DBMS the initial time, read this
+    section too, it might give you a guideline on how to set up backup
     and restore procedures (at least the strategy for building
     them) which are sufficient for your needs and for the safety
@@ -171 +182 @@
 
     <sect3>
-      <title>Upgrade by system tools</title>
+      <title>Upgrade data file by using system tools</title>
 
       <para>