Comment 2 for bug 142358

The tpc_begin(), abort(), tpc_abort() sequence looks normal to me. The transaction got started, something went wrong in the middle (like a ConflictError), so the current transaction was aborted. An abort during 2PC requires that we call abort() for each object and then call tpc_abort().

Is there some specific problem or unusual behavior you are seeing? Or are you just nervous about log messages you haven't seen before?