You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Avoid repeated decoding of prepared transactions after a restart.
In commita271a1b, we allowed decoding at prepare time and the preparewas decoded again if there is a restart after decoding it. It was donethat way because we can't distinguish between the cases where we have notdecoded the prepare because it was prior to consistent snapshot or we havedecoded it earlier but restarted. To distinguish between these two cases,we have introduced an initial_consistent_point at the slot level which isan LSN at which we found a consistent point at the time of slot creation.This is also the point where we have exported a snapshot for the initialcopy. So, prepare transaction prior to this point are sent along withcommit prepared.This commit bumps SNAPBUILD_VERSION because of change in SnapBuild. Itwill break existing slots which is fine in a major release.Author: Ajin Cherian, based on idea by Andres FreundReviewed-by: Amit Kapila and Vignesh CDiscussion:https://postgr.es/m/d0f60d60-133d-bf8d-bd70-47784d8fabf3@enterprisedb.com