Just a quick note, in case you see worse performance with Postgres than with SQLite...
Postgres (by default) does an fsync() or an fdatasync() (can't remember which) after every write to the database files, (similar default behaviour to SQLite 3.0) which can hamper performance, but with increased resiliency. Since you can (in case of disaster) recreate the catalog using bscan, I would be tempted to run the catalog database without this option, and take my chances (assuming I saw a noticeable performance increase with the sync option off). See the Postgres FAQ "How do I tune the database engine for better performance?" http://www.postgresql.org/docs/faqs.FAQ.html#3.3 Pay special note to the "Server configuration" section. By tuning your DBMS, you should be able to get a noticeable performance boost (the same applies to MySQL, and probably to SQLite too). Note that I'm still using SQLite 2.x here. -- Russell Howe [EMAIL PROTECTED] ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
