> an interceptor that creates and cleans up the transaction for you. I'm not sure about the word "interceptor" here because in Go and every other language I kn

> an interceptor that creates and cleans up the transaction for you. I'm not sure about the word "interceptor" here because in Go and every other language I know which does this it is merely a wrapper, but Go does this. From some vantage, the problem only arises because Go does this - if it instead forced you to create a transaction the resource allocation, and so possibility of exhaustion, would be a lot more obvious.