The job table is probably not causing the bloat, unless you have millions of
rows.  The space is usually consumed by the file table and its indexes.

Try running vacuumdb with the --analyze and --verbose options, which prints
info about the number of pages used by each table/indexes and also the number
of unused rows.  You can also get info from the SQL query

SELECT relname, reltuples, relpages FROM pg_class ORDER BY relpages DESC;

Which version of postgresql are you using?  With postgresql 7, I found that
regularly doing reindex on the file table indexes was needed to prevent bloat.

__Martin

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users