ebl update sqlite convertion doc

diff --git a/docs/manuals/en/catalog/catmaintenance.tex b/docs/manuals/en/catalog/catmaintenance.tex
index f0abaa6fe614b28eea5c17672e2b6ac3196877b4..07b1b6b6b688d05fee77c12e5645c4de49a8533d 100644 (file)
--- a/docs/manuals/en/catalog/catmaintenance.tex
+++ b/docs/manuals/en/catalog/catmaintenance.tex
@@ -524,18 +524,18 @@ Director's configuration file. Note, in the case of SQLite, it is necessary to
 completely delete (rm) the old database before creating a new compressed
 version. 
 
-\section{Migrating from SQLite to MySQL}
+\section{Migrating from SQLite to MySQL or PostgreSQL}
 \index[general]{MySQL!Migrating from SQLite to }
-\index[general]{Migrating from SQLite to MySQL }
+\index[general]{Migrating from SQLite to MySQL or PostgreSQL}
 
 You may begin using Bacula with SQLite then later find that you want to switch
-to MySQL for any of a number of reasons: SQLite tends to use more disk than
-MySQL; when the database is corrupted it is often more catastrophic than
-with MySQL or PostgreSQL.
-Several users have succeeded in converting from SQLite to MySQL by
-exporting the MySQL data and then processing it with Perl scripts
-prior to putting it into MySQL. This is, however, not a simple
-process.
+to MySQL or Postgres for any of a number of reasons: SQLite tends to use more
+disk than MySQL; when the database is corrupted it is often more catastrophic
+than with MySQL or PostgreSQL.  Several users have succeeded in converting by
+exporting the SQLite data and then processing it with Perl scripts prior to
+putting it into MySQL or PostgreSQL. This is, however, not a simple process.
+Scripts are available on bacula source distribution under
+\texttt{examples/database}.
 
 \label{BackingUpBacula}
 \section{Backing Up Your Bacula Database}