Hm I can try it without the patches but what I wanted was to make sure my admittedly very naive approach of just popping two messages was appropriate when the backend failed as opposed to us writing a `CopyFail` message. The 2.times part is to ensure that the connection is left in such a state that it can actually be reused well. I copied that idea from the tests for the same functionality in Sequel for their postgres adapter. The best way to test that the state is left in an appropriate position is to move it again?