On Sunday 20 December 2009 20:59:05 Eric Bollengier wrote: > Le dimanche 20 décembre 2009 19:26:43, Eric Bollengier a écrit : > > Postgres gives an API call to determine if the client is thread-safe or > > not, perhaps MySQL do the same (i will check). > > MySQL API has mysql_thread_safe() (found on 3.1/4.0 manual) > PostgreSQL has PQisthreadsafe() (but only for >= 8.2) > SQLite3 has sqlite3_threadsafe() > > Do you think that possible to test the result of this function in the > ./configure ? (I would say yes, and i can look tomorrow)
Yes, it is possible, but a bit ugly to do. > > We can use the old way as workaround for postgresql 8.0, and 8.1 What I suggest is I change the current code in configure so that it complains but it does not disable batch insert. Then we add new code that uses the API calls and if batch insert is turned on when we try to open a connection and thread safe is not enabled, we M_ABORT Bacula. For old postgres versions, we warn the user in the documentation. Kern ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
