On 14/09/10, Tobias Brink (tobias.br...@gmail.com) wrote: > You should also be careful with the 5.0.2-1 version if you use > Postgres: it broke my database on upgrade. This is fixed in 5.0.2-2 > which is not (yet?) in the backports. See also > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591293 which seems to > include a workaround.
You can deal with the problem by dropping the file_jpfid_idx index prior to the upgrade. You will not lose any data if you do this and have to revert to your pre-upgrade database, although it would be wise to recreate the index as file-related sql queries will be dramatically slower! As John Goerzen notes in Tobias' linked bug report, one can recreate the index as follows: CREATE INDEX file_jpfid_idx on file (jobid, pathid, filenameid); -- Rory Campbell-Lange r...@campbell-lange.net ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
