odbc threading

最新推荐文章于 2024-08-28 14:02:01 发布

whyhonest

最新推荐文章于 2024-08-28 14:02:01 发布

阅读量1k

点赞数

CC 4.0 BY-SA版权

文章标签： postgresql resources

本文链接：https://blog.youkuaiyun.com/whyhonest/article/details/8002056

本文深入探讨了ODBC配置文件odbcinst.ini中关于PostgreSQL驱动的不同版本设置及其线程控制策略，尤其针对FreeSWITCH环境下高并发场景下线程配置的重要性进行了详细说明。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

odbcinst.ini Threading=0

[PostgreSQL ANSI] 
Description            = PostgreSQL ODBC driver (ANSI version)
Driver          = /usr/lib/odbc/psqlodbca.so
Setup           = /usr/lib/odbc/libodbcpsqlS.so
Debug           = 0
CommLog         = 0
UsageCount              = 0
Threading = 0

[PostgreSQL Unicode]
Description             = PostgreSQL ODBC driver (Unicode version)
Driver          = /usr/lib/odbc/psqlodbcw.so
Setup           = /usr/lib/odbc/libodbcpsqlS.so
Debug           = 0
CommLog         = 0
UsageCount              = 0
Threading = 0
MaxLongVarcharSize=65536

Also note, (see bug below on bottom of page); If you are using the FreeSWITCH pooled resources, then you definitely need Threading = 0 for high call volume. What this does is it "disables a global mutex in the ODBC core that only allows 1 concurrent operation per process regardless of the concurrent connections." (i.e. It slows down when you have too many connections trying at one time)

As far as has been tested, when making changes to the odbcinst.ini, you do not need to restart FreeSWITCH to effect the changes.