Marco wrote: > One interesting thing is the prepared transaction name generated by > the coordinator, which follows the form: citus_<coordinator node > id>_<pid>_<server-wide transaction number >_<prepared transaction > number in session>. The server-wide transaction number is a 64-bit > counter that is kept in shared memory and starts at 1. That means that > over 4 billion (4207001212) transactions happened on the coordinator > since the server started, which quite possibly resulted in 4 billion > prepared transactions on this particular server. I'm wondering if some > counter is overflowing.
Amit wrote: >Interesting. This does kind of gets us closer to figuring out what >might have gone wrong, but hard to tell without the core dump at hand. If something is corrupting memory rarely. It would be interesting to consider all the possibilities. The MemSet function has an error alert on line 785 (twophase.c). The size the var "_vstart" buffer, is not multiple size of the type long. Maybe it's filling more than it should. Ranier Vilela
