Closed albertov closed 6 years ago
@albertov, I believe this problem should be fixed now by preventing the condition that causes it (sending a spurious Sync when a ReadyForQuery is already on the way). If you still see this problem, please reopen an issue.
I've built my app against the current head and been running tests continuously for about 20 minutes and no issues so far (IIRC, I should have seen the error I mentioned by now). I'll reopen if I see the problem again. Thanks!
Thanks for the report. I think I see what could cause this, and have reproduced a form of it with a high-latency connection, but I suspect this could happen for other calls as well. I'm working on a more general fix, and with integrate this with that.