Closed benbro closed 4 years ago
Thanks, it looks like its a case of using a tuple instead of a record biting me. Specifically on that line matching on a 4-tuple instead of a 5-tuple.
Can you explain when it happens? Is there a quick fix? I'm getting this error in production.
I can do the quick fix.
I think that function is called when the process using the connection from the pool crashes. To be safe it disconnects that connection and creates a new one.
Pushed to master. Can you try that?
I'll try adding a test that reproduces it and verifies the fix before releasing to hex.
Verified with a test and pushed that to master. Will make a hex release now.
Published pgo 0.11.1
Thank you for the quick fix. I've upgraded to pgo 0.11.1 in production with a manual fix for the transaction issue.
I got this error in the log: