On Wednesday 27 January 2010 13:27:10 Eric Bollengier wrote: > Hi, > > Le mercredi 27 janvier 2010 13:10:51, Kern Sibbald a écrit : > > Then there is no way for us to check 100% that it is thread save, which > > means that with the current, conservative logic there is no way to turn > > on batch insert. > > > > Theoretically if the library name ends in _r.so, it should be thread > > safe, but we currently do not have any code to check for that. > > > > If I am not mistaken, we now have runtime code that checks whether or not > > the library is thread safe (absolutely required for batch insert), but > > I think it is only implemented for Postgesql. Eric can confirm this. > > It's implemented for MySQL, SQLite and PostgreSQL.
Thanks for the update. However, whould it be possible to first modify the db_check_backend_thread_safe() code to print an error and then disable all batch inserts, with another error message in each Job that tells the user that the batch insert is disabled? One of the problems I see at least for PostgreSQL is that the check only works on later versions, I now recall is the reason we left the ./configure check in. > > > If we have valid runtime code for all libraries, we could remove the > > current checks during configure time that require the .a. Perhaps for 5.0.1 we can eliminate the code in configure.in that checks to .a file. Regards, Kern ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
