if you have older unixodbc edit /etc/odbcinst.ini and add the param Threading=0 to each db entry.<div>I like postgres better but that's mostly a personal preference from watching both of them grow up over the years.</div>
<div><br></div><div>The only thing that crashes in ODBC is bad drivers typically. With mysql you often need to specify the "threadsafe" one by editing odbc.ini and adding in the _r to the name of the mysql driver .so file.</div>
<div><br></div><div>In general postgres to me appears to care more about multithreaded environments and with the above threading=0 change works pretty well.</div><div><br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">
On Wed, Oct 26, 2011 at 5:40 AM, Patrick Lists <span dir="ltr"><<a href="mailto:freeswitch-list@puzzled.xs4all.nl">freeswitch-list@puzzled.xs4all.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 10/26/2011 06:49 AM, Hynek Cihlar wrote:<br>
> That being said, unixODBC 2.2 will often segfault under that load, so be<br>
> wary of that (it appears reliable up to about 300 connections, seems to<br>
> reliably fall over at 330). We're in the process of testing 2.3.0 which<br>
> is reportedly better in this regard.<br>
><br>
><br>
> This is unfortunate! I was planning to cluster several freeswitch<br>
> instances through the DB server. But if the unixODBC crashes under high<br>
> load, it is a major issue in this regard as there are not many options<br>
> left to implement the cluster.<br>
<br>
</div></div>If you use Red Hat RHEL or CentOS and there is a crash with stock<br>
unixODBC (2.2) then a bug should be reported at <a href="http://bugzilla.redhat.com" target="_blank">bugzilla.redhat.com</a>. In<br>
my experience such bugs do get fixed.<br>
<br>
Regards,<br>
<font color="#888888">Patrick<br>
</font><div><div></div><div class="h5"><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900<br>
</div>