Bruno Friedmann wrote:
> Hello Eric,
>
> On 12/14/2009 10:37 AM, Eric Bollengier wrote:
>   
>> Hello Bruno,
>>
>> You should find this information in the configure output (at the end), or
>>     
>
> This is what we can't have when we are using binary only installed files.
> There's no like /proc/config.gz in bacula :-)
>
>   

Yes, we are thinking about adding this information to the binary for 
easier support.

>> you may find this information by using "strings" on the bacula-dir binary
>> (or maybe the libbacsql file)
>>
>> strings bacula-dir | grep batch
>> CREATE TEMPORARY TABLE batch
>>
>> Bye
>>
>>     
>
> ok I've try and only get this on the two proposed
>
> strings /usr/sbin/bacula-dir | grep batch
> _Z27db_write_batch_file_recordsP3JCR
> _Z23db_open_batch_connexionP3JCRP4B_DB
>
> Which leave me a bit perplex !
>   

Please, the the whole sentence, if you are using Bacula 3.0.x with 
libtool support, you
need also to check the libbacsql object. (where the SQL code resides)

> People around are certifing that it was a batch-insert enabled ...
>
> During a backup I didn't see mysql using a tmp file somewhere or using a tmp 
> table in processlist.
>
> Did batch-insert also work with MyIsam tables ?
>   

Yes, but be aware that MyISAM and Innodb doesn't let you insert bulk 
data in parallel. This
can be a performance problem in big setups.

Bye
> I think I should rebuild a real enabled batch-insert or did you have anoter 
> idea.
>
>
>   
>> Bruno Friedmann wrote:
>>     
>>> Hi all,
>>>
>>> I need to know if a bacula-dir binary has or not batch-insert-enabled.
>>> Is there a simple (or complex) way to do this ?
>>>
>>> Thanks for tips.
>>>
>>>   
>>>       
>
>
>   


------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to