Hello all,
I'm not sure if this is a bug or not, but I'm running Bacula 2.2.1 (granted
I see that 2.2.3 just came out today so I'll download and install to see how
it works), but after going through the Bacula Tutorial (and I'm using
PostgreSQL 8.1.9), running drop_bacula_tables (after I had successful run a
backup test and restore per chapter 9 of the tutorial), which calls
drop_postgresql_tables, there results of dropping the tables yields and
error regarding a table allegedly named "mac" (as can be seen from my output
below.
I'm not sure what the "mac" table's purpose is and if it should have been
created in the first place (with the make tables scripts)? I took a look at
the make_postgresql_tables and I didn't see a table named "mac" or "MAC"
listed.
Should then drop_postgresql_tables be updated to no longer attempt to drop
the "mac" table?
Thanks,
-H
DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> DROP TABLE
> psql:<stdin>:19: ERROR: table "mac" does not exist
> DROP TABLE
> DROP TABLE
> DROP TABLE
> Deletion of Bacula PostgreSQL tables succeeded.
> Dropped PostgreSQL tables
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
