Comments on: Ruby and mysqlplus select() deadlock

By: coderrr

coderrr — Sat, 18 Apr 2009 23:13:52 +0000

Yea both those unsynchronized ||=’s could be it

roger — Sat, 18 Apr 2009 23:09:40 +0000

I am wondering if the problem was that there was no concurrency lock around the assignment to @sockets ?

MySQL vs PostgreSQL в ActiveRecord | Uniвсячина — Tue, 24 Feb 2009 23:08:19 +0000

[...] о такой поделке, как драйвер MySqlPlus. Но лично мне, как-то ссыкотно его запускать на [...]

roger — Mon, 12 Jan 2009 20:09:18 +0000

yeah mysqlplus will compile on 1.9.
I was wondering more of the
remove_bad_fds
stuff is necessary for 1.9

I almost wonder if, like Python, the select function should raise on the thread that passed it a bad descriptor.

Yeah windows is definitely the step child of Ruby land, though I hear jruby actually runs on it with reasonable speed :)
-=r

coderrr — Mon, 12 Jan 2009 20:01:54 +0000

Haven’t tried on 1.9, is mysqlplus 1.9 compat?

Windows? lol

roger — Mon, 12 Jan 2009 19:58:49 +0000

does 1.9 have this bug? Does the patch work on windoze :) ?
-=r

roger — Mon, 12 Jan 2009 18:46:46 +0000

k I updated it to default to the c_async_query as you described. Let me know if it doesn’t work.

I’d recommend the bug listed be submitted to ruby-core, too :)

-=r

ActiveRecord threading issues and resolutions « coderrr — Sun, 11 Jan 2009 19:08:02 +0000

[...] I ran into a deadlock with the Ruby implementation of async_query, so use the C one instead. Then add this somewhere so [...]