Changeset 7a9a7b26 for server/databases/upgradedb.xml

Timestamp:

04/20/2022 01:36:11 PM (2 years ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

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, xry111/llvm18, xry111/soup3, xry111/xf86-video-removal

Children:

82b6f40

Parents:

9a06e3e

Message:

Remove spaces at the end of lines

File:

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

server/databases/upgradedb.xml

@@ -18 +18 @@
     when an existing database is in use.  It is not applicable for
     initial installations or if there is no existing database for
-    the package being updated, but users should read through it 
+    the package being updated, but users should read through it
     to become aware of issues that can arise in the future.</para></note>
 
@@ -33 +33 @@
 
 Oct 26 17:11:53 SVRNAME systemd[1]: Starting PostgreSQL database server...
-Oct 26 17:11:53 SRVNAME postgres[17338]: 2021-10-26 17:11:53.420 CDT [17338] FATAL:  
+Oct 26 17:11:53 SRVNAME postgres[17338]: 2021-10-26 17:11:53.420 CDT [17338] FATAL:
                 database files are incompatible with server
-Oct 26 17:11:53 SRVNAME postgres[17338]: 2021-10-26 17:11:53.420 CDT [17338] DETAIL:  
+Oct 26 17:11:53 SRVNAME postgres[17338]: 2021-10-26 17:11:53.420 CDT [17338] DETAIL:
                 The data directory was initialized by PostgreSQL version 13,
                 which is not compatible with this version 14.0.
@@ -134 +134 @@
         <listitem>
           <para>Create a full database backup using the old tools.</para>
-          
+
           <para>This step creates an offline copy of the database files ready
           to be used for long term archiving, for disaster recovery, or just
@@ -158 +158 @@
           to fully protect your data, create a backup of the corresponding old
           binaries (and/or their sources) and store it along with the data
-          files to make sure that there is a fallback solution if 
-          the newer software is not able to read the older data.</para> 
-          </listitem> 
-
-          <listitem> 
-            <para>Upgrade the server software</para> 
+          files to make sure that there is a fallback solution if
+          the newer software is not able to read the older data.</para>
+          </listitem>
+
+          <listitem>
+            <para>Upgrade the server software</para>
 
             <para>In this step, instructions to build the database server
             software are executed just as they are shown in subsequent sections
             talking about the DBMs like MariaDB or Postgresql. That is, build
-            the software as usual using BLFS instructions.</para> 
-          </listitem> 
-
-          <listitem> 
-            <para>Restore the database by using the new tools.</para> 
+            the software as usual using BLFS instructions.</para>
+          </listitem>
+
+          <listitem>
+            <para>Restore the database by using the new tools.</para>
 
             <para>To restore the data, the tools of the newly installed server
@@ -179 +179 @@
             software requires. It is assumed that newer software is capable of
             reading old data.</para>
-          </listitem> 
+          </listitem>
           </itemizedlist>