>> Also, I noticed in the current "limitations" that 4 billion files is >> the limit per database? (this would I assume be per director then in >> reality if they used different databases?) > > Actually, it's per-database catalog. This is because most databases > use 32 bit int for IDs.
You can use bigint instead of integer and bigserial instead of serial in your make_postgresql_tables. > You can have multiple databases (what Bacula calls a catalot) per Bacula > director, which allows you to get around this. Each catalog can only > have 4 billion files. You can use 64bit FileId_t..., It works with our postgresql database - cats/cats.h:typedef uint32_t FileId_t; - jcr.h: uint32_t FileId; /* Last file id inserted */ + cats/cats.h:typedef uint64_t FileId_t; + jcr.h: uint64_t FileId; /* Last file id inserted */ Regards ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
