Hi, I've spent today quite a bit of time to figure out why pg gem doesn't work with Merb and Sequel and why the hell Merb ends in loop and eats 100% CPU.
The bad is that I didn't find a solution to the problem. The problem seems to be somewhere during Merb reloads model classes which triggers Sequel to query DB for schema information. After the first query to the database connection is lost and not removed from the Sequel connection pool which raise Sequel::DatabaseDisconnectError. This happen in both drivers (postgres or pg). But in pg you end in infinite loop issuing huge amount of syscalls. I tried to disconnect and cleanup the Sequel connection pool, but it doesn't have any effect. I tried on MacOS and Ubuntu with the same bad results. I also tried to reproduce problem in Sinatra but without succes, everything worked. Anyody ideas???? For now I'll add warning mesage to merb_sequel saying to gem uninstall pg or give up reloading and just use manual restarts. You have to uninstall the gem because sequel loads it and bundling doesn't help. I'll post to the ruby-pg as well. Pavel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
