Amit Kapila 8bdb1332eb Avoid repeated decoding of prepared transactions after a restart. ... In commit a271a1b50e, we allowed decoding at prepare time and the prepare was decoded again if there is a restart after decoding it. It was done that way because we can't distinguish between the cases where we have not decoded the prepare because it was prior to consistent snapshot or we have decoded it earlier but restarted. To distinguish between these two cases, we have introduced an initial_consistent_point at the slot level which is an 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 initial copy. So, prepare transaction prior to this point are sent along with commit prepared. This commit bumps SNAPBUILD_VERSION because of change in SnapBuild. It will break existing slots which is fine in a major release. Author: Ajin Cherian, based on idea by Andres Freund Reviewed-by: Amit Kapila and Vignesh C Discussion: https://postgr.es/m/d0f60d60-133d-bf8d-bd70-47784d8fabf3@enterprisedb.com		2021-03-01 09:11:18 +05:30
..
expected	Avoid repeated decoding of prepared transactions after a restart.	2021-03-01 09:11:18 +05:30
specs	Fix the test for decoding of two-phase transactions.	2021-01-09 15:45:38 +05:30
sql	Raise a timeout to 180s, in contrib/test_decoding.	2021-02-27 07:02:56 -08:00
.gitignore	Improve isolation tests infrastructure.	2017-03-14 15:56:17 -07:00
Makefile	Test decoding of two-phase transactions during the build of a consistent snapshot.	2021-01-05 15:05:22 +05:30
logical.conf	Add logical_decoding_work_mem to limit ReorderBuffer memory usage.	2019-11-19 07:32:36 +05:30
test_decoding.c	Update copyright for 2021	2021-01-02 13:06:25 -05:00