Richard Braakman wrote:
> Hmm... if conn_destroy is being called in a context where it is still > possible that some other process has a lock on the connection, then > something is wrong. conn_destroy should only be called on connections > that are definitely not in use anymore. The connection is not "in use", it's just that a thread has called conn_register() for it with no intention to use it later. Without the fix the callback function can not safely destroy the connection without further synchronization.
