Hello,
The Bacula PostgreSQL schema is missing several foreign keys (FK). Foreign keys
are not a new database concept; they've been around for decades. They are
reliable and robust.
Wednesday, I started a dbcheck on a Bacula database. Granted, that database is
19 years old and this is the first time I've run dbcheck (as far as I know).
That dbcheck is still going. FYI, the dump to disk is about 140GB; lots of
cruft removal.
When PostgreSQL was first added to Bacula, there was resistance to FK, and I
did not pursue the issue. Thus, it persists to this day. I hope to change that.
I would like to take that development work back up (pun intended), and start
adding foreign keys back into Bacula, at least for PostgresQL. That might
remove the need for dbcheck (again, at least for Bacula on PostgreSQL).
For example, one index I have been using this index for years. I find it
referenced[1] in the the 5.x documentation, but it is not part of the catalog
creation.
"file_jobid_idx" btree (jobid)
This index vastly improves the construction of the files, often going from
hours to seconds. I don't recall when that index was added here, but building
trees has never been an issue here.
I have no timeline for this work, but just posting the intent often gives me
the incentive to get started.
1 - https://www.bacula.org/5.2.x-manuals/en/main/main/Catalog_Maintenance.html
--
Dan Langille
d...@langille.org
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
