Jan Vroonhof <vroonhof(a)math.ethz.ch&gt; writes in xemacs-beta(a)xemacs.org: Is the module code stable now? And, are modules built by default? Personally, I'd prefer it not being a module by default, because libpq is lightweight and linked shared by default and the Lisp binding is lightweight (~13k with full debugging enabled). The same issue exists on cleaning up PGresult variables. In my testing, calling `pq-final' was an insta-crash. How do I do this correctly? Can I force PGconn and PGresult variables to never be copied? I'm providing a low-level, policy-free binding to the library. This functionality can be done easily in additional Lisp code. I got asynchronous queries[1] working last night. Cursors should work for free since they're implemented by the Postgres backend in SQL. I'll try that this afternoon. It is. Footnotes: [1] The don't buy near as much as I hoped due to unexpected apparent utter brain damage in the XEmacs event code.