[Dbconfig-common-devel] dbconfig-common/doc dbapp-policy.html,1.5,1.6 dbconfig-common-design.html,1.4,1.5 dbconfig-common-using.html,1.5,1.6 dbconfig-common.html,1.5,1.6

[Karsten Hilbert]

>  <p>
> -before a package is upgraded, it should make a backup of any database
> -in the case of error.
This is very prudent.

>  the backup should be performed early, ahead of
> -the new package being unpacked.  this ensures that the versions of the
> -software necessary to interact with the previous version of the database
> -are present, since newer versions of the tools might not necessarily
> -be compatible.
In PostgreSQL the recommended procedure is to use the pg_dump
of the *newer* version, however.

Taken together this probably means that one should

a) make a backup with the old version before changing anything
   just to be on the safe side
b) make a second backup intended for restoring into the new
   database version as soon as the new dump utility is
   available

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346