Helpful error message when a result set is not closed

[straight-shoota]

Executing a query on the same connection while a previous result set is still open can lead to weird errors because of unexpected data is sent. It's hard to figure out why it's failing.

An example for this situation:

conn.query_all sql do |rs|
  conn.exec other
end

Is it possible to detect if there is still an unclosed result set hanging around and raise with a friendly error message which explains this?

I encoutered this problem with the PG driver but it's probably similar with others as well.