Just about parameter naming: you can't actually enable\disable a type =) So
either parameter name should be, let's say, db_table_lock_write, or it
should accept locking type as a parameter.
2015-01-16 15:24 GMT+03:00 Richard Good <richard.good(a)smilecoms.com>om>:
Hi
We have noticed when using pua module with db_mode set to 1 the lock type
defaults to DB_LOCKING_WRITE which locks the whole table and can cause
performance issues.
I noticed this fix for the presence module last year specifically on this
issue:
http://lists.kamailio.net/pipermail/sr-dev/2014-January/022820.html
I've attached an almost identical patch for pua I want to commit. The
patch makes this a configurable parameter that defaults to DB_LOCKING_WRIT.
If no one raises any concerns I will go ahead and commit.
Regards
Richard.
This email is subject to the disclaimer of Smile Communications at
http://www.smilecoms.com/home/email-disclaimer/
<http://www.smilecoms.com/disclaimer>
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Best regards,
Alekzander Spiridonov