Hi, 23.09.2007 15:15,, Marc Cousin wrote:: >> You shouldn't concern yourself with the "batch" table. It is a temp table >> and there is no need to create.
Or rather, that's the way it should be. >> Your problem has nothing to do with the batch insert code itself, but >> simply that it is turned off for some unknown reason. >> >> Regards, >> >> Kern >> > > Anyway, doesn't it seems like the batch code is only partially turned off ? Yes, that seems to be the point. In fact, on that system, Bacula was reinstalled with the configure option --disable-batch-insert and the problem persists. So I can only conclude that currently, even if batch inserts *should* be disabled, they are not. > If batch inserts are disabled, the code shouldn't try to use the batch table > at all, it should still work the 'old' way, by working directly into the > target tables... > > Of course batch should be on in this config, but if configure says it's off, > we shouldn't have these messages. > > Maybe I'm missing something, but I feel something's strange... So do I. And Ondrej has the same problem... there must be problem with configure and/or the source code. Arno -- Arno Lehmann IT-Service Lehmann www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
