--Da: Magnus Hagander <[EMAIL PROTECTED]>A: Dan Langille <[EMAIL PROTECTED]> Gabriele Bulfon <[EMAIL PROTECTED]> Cc: bacula-users@lists.sourceforge.net Data: 26 settembre 2006 15.56.15 CESTOggetto: RE: [Bacula-users] Postg
Hello,I enabled full logging of connections/statements on Postgres to see what happens when bconsole hangs.Analyzing the log I can see that during startup the Director runs some statements succesfully, then something goes wrong when I use the bconsole.Anyone know what is the meaning of these erro
> > 2006-09-26 14:06:51 LOG: database system is ready
> > 2006-09-26 14:06:51 LOG: transaction ID wrap limit is
> 2147484148, limited by database "postgres"
> > 2006-09-26 14:06:51 LOG: autovacuum: processing database
> "bacula"
>
> There, a vacuum begins. Bacula is not doing that.
Vaccum/aut
Autovacuum is never enabled on my installations, because postgres is usually version 8.0.This log was from my personal installation of postgres on a laptop, for testing purposes, and because it is 8.1, it has autovacuum enabled by default.I tried disabling autovacuum as you suggested anyway, but
On 26 Sep 2006 at 14:17, Gabriele Bulfon wrote:
> Hello,
> I enabled full logging of connections/statements on Postgres to see what
> happens when bconsole hangs.
> Analyzing the log I can see that during startup the Director runs some
> statements succesfully, then something goes wrong when I u
