Question

How do I resolve the error message "Current transaction id has moved backwards"?

Environment

Connector: PostgreSQL

Answer

A historical re-sync is required.

Cause

When the transaction ID has moved backward, this usually means that we have been connected to a different database instance (this could be from master to replica, or from one replica to another, or if a database has moved to a new server, etc.). We will be indefinitely waiting for the transaction ID to catch up, so a re-sync is required.