Sam Saffron <[email protected]> wrote:
> 1. Is this a pg bug? How could they even implement a ubf in such a way
> that it does not stop queries when signals are sent? The main issue is
> that without this Thread.kill will have to wait for queries to finish.
No, not a pg bug. pg needs to account for the user hitting Ctrl-C and
wanting to cancel a query (oh-no-I-started-DELETE-without-WHERE!).
> 2. Is this a ruby bug? should there be a more sophisticated protocol
> here? Should trap handlers inform the runtime that a ubf is not
> needed?
I don't know. Something like: trap(:QUIT, no_ubf: true) { ... } ?
> something else ?
Also see http://mid.gmane.org/[email protected]
Btw, given the master <-> worker separation in unicorn, we can also
have the master talk to the worker through a pipe and avoid signals
between the two.
> Similar issue exists in mysql afaik.
I don't think the mysql2 gem currently interrupts running queries.
Not sure about the others.
_______________________________________________
Unicorn mailing list - [email protected]
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
