Lucas Hope escribió: > I get this sometimes when I have done a "wrong" query that is wrong in > that it would take a very long time to complete, not a malformed SQL > statement. > > Then I interrupt the process from the lisp/slime side, but the > PostgreSQL side is still happily executing. The toplevel connection is > still waiting for the result, and hence you have to reconnect toplevel > (or better, kill the rogue postgres process). > > This behaviour seems correct to me, or at least suitable enough. A > minor improvement might be to kill the query if you interrupt and > cancel the lisp-side process, but that sounds like too much trouble. > > So it depends how "wrong" wrong is. Mmm...maybe that's what is happening. I'll check. Thanks
Mariano _______________________________________________ postmodern-devel mailing list postmodern-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel
