> my postgresql-log got errors about a missing table ( and an > index on it) now the wired thing is that table is not defined > in the create script at all (checked with CVS) > > wtf is wrong here ?
Nothing. Bacula forcibly deletes these these objects even if they don't exist, to make sure they go away, and then recreate it automatically. It's just a temporary working table. One could use DROP IF EXISTS I guess, but that would then require postgresql 8.1, which is a bit too limiting right now. Bottom line - not a problem, just ignore the errors for that table. > it's working like that but i can't backup database since > postgresql is complaining about missing transaction logs, > probably due to those errors ? No, postgresql transaction log errors have nothing to do with what's in your database. What exactly is the error you get about the logs? //Magnus _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
