mirror of
https://github.com/Zeckmathederg/glfs.git
synced 2025-01-24 23:32:12 +08:00
Textual changes
This commit is contained in:
parent
bcdfc536eb
commit
7f6bf79b05
@ -12,7 +12,12 @@
|
||||
<date>$Date$</date>
|
||||
</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
|
||||
-- postgresql.service - PostgreSQL database server
|
||||
@ -38,8 +43,14 @@ Oct 26 17:11:53 SRVNAME systemd[1]: Failed to start PostgreSQL database server.<
|
||||
upgrade.
|
||||
</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
|
||||
of your data.
|
||||
@ -170,7 +181,7 @@ Oct 26 17:11:53 SRVNAME systemd[1]: Failed to start PostgreSQL database server.<
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Upgrade by system tools</title>
|
||||
<title>Upgrade data file by using system tools</title>
|
||||
|
||||
<para>
|
||||
Some database systems (for instance Postgresql) provides
|
||||
|
Loading…
Reference in New Issue
Block a user