I get this sometimes when I have done a &quot;wrong&quot; query that is wrong in that it would take a very long time to complete, not a malformed SQL statement.<br><br>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).<br>
<br>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.<br><br>So it depends how &quot;wrong&quot; wrong is.<br>
<br>-Luke<br><br><div class="gmail_quote">On Sat, Mar 20, 2010 at 9:17 AM, Marijn Haverbeke <span dir="ltr">&lt;<a href="mailto:marijnh@gmail.com">marijnh@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello Mariano,<br>
<br>
I haven&#39;t seen this issue before. Are those queries made from the<br>
REPL, or from another thread? Also, which CL implementation, and which<br>
Postgres version are you using?<br>
<br>
Best,<br>
<font color="#888888">Marijn<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
postmodern-devel mailing list<br>
<a href="mailto:postmodern-devel@common-lisp.net">postmodern-devel@common-lisp.net</a><br>
<a href="http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel" target="_blank">http://common-lisp.net/cgi-bin/mailman/listinfo/postmodern-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>---------------------------------------------------<br>Dr Lucas Hope - (646) 2332123 after 3pm US EST<br>Machine Learning and Software Engineering Consultant<br>
Melbourne, Australia<br>