From: Eric Bollengier Date: Sat, 28 Mar 2009 14:02:56 +0000 (+0000) Subject: ebl document dbcheck.sql X-Git-Tag: Release-3.0.0~81 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=8590fb84d8e08fb46512eab04f33fdf4077ddbc2;p=bacula%2Fdocs ebl document dbcheck.sql --- diff --git a/docs/manuals/en/utility/progs.tex b/docs/manuals/en/utility/progs.tex index f45f4fa8..5213fc3d 100644 --- a/docs/manuals/en/utility/progs.tex +++ b/docs/manuals/en/utility/progs.tex @@ -1192,6 +1192,16 @@ The inconsistencies examined are the following: If you are using Mysql, dbcheck will ask you if you want to create temporary indexes to speed up orphaned Path and Filename elimination. +Mostly for PostgreSQL users, we provide a pure SQL script dbcheck replacement +in \url{examples/database/dbcheck.sql} that works with global queries instead +of many small queries like dbcheck. Execution instructions are at the top of +the script and you will need to type \texttt{COMMIT} at the end to validate +modifications. + +If you are using bweb or brestore, don't eliminate orphaned Path, else you will +have to rebuild \texttt{brestore\_pathvisibility} and +\texttt{brestore\_pathhierarchy} indexes. + By the way, I personally run dbcheck only where I have messed up my database due to a bug in developing Bacula code, so normally you should never need to run dbcheck in spite of the