Add an extra catch for RuntimeException in the postgreOperatorStatement.

This is to address a `CursorLifecycle$WrongStateException` for a performance_dashboard query. The exception being show occurs because the execution phase throws an exception (but not an IOException), which is then lost when the `finally { close() }`, when the operator stack is in the wrong state, tries to close the cursors. 

Now catch the relevant exceptions, log both, and re-throw the more important one.