Fix bug in WAL replay of COMMIT_TS_SETTS record.

MasaoFujii · MasaoFujii · commit c29bab799c82 · 2021-03-25T11:25:34.000+09:00
Previously the WAL replay of COMMIT_TS_SETTS record called TransactionTreeSetCommitTsData() with the argument write_xlog=true, which generated and wrote new COMMIT_TS_SETTS record. This should not be acceptable because it's during recovery. This commit fixes the WAL replay of COMMIT_TS_SETTS record so that it calls TransactionTreeSetCommitTsData() with write_xlog=false and doesn't generate new WAL during recovery. Back-patch to all supported branches. Reported-by: lx zou <zoulx1982@163.com> Author: Fujii Masao Reviewed-by: Alvaro Herrera Discussion: https://postgr.es/m/16931-620d0f2fdc6108f1@postgresql.org
diff --git a/src/backend/access/transam/commit_ts.c b/src/backend/access/transam/commit_ts.c
@@ -1012,7 +1012,7 @@ commit_ts_redo(XLogReaderState *record)
 			subxids = NULL;
 
 		TransactionTreeSetCommitTsData(setts->mainxid, nsubxids, subxids,
-									   setts->timestamp, setts->nodeid, true);
+									   setts->timestamp, setts->nodeid, false);
 		if (subxids)
 			pfree(subxids);
 	}

Original file line number	Diff line number	Diff line change
`@@ -1012,7 +1012,7 @@ commit_ts_redo(XLogReaderState *record)`
`1012`	`1012`	`subxids = NULL;`
`1013`	`1013`
`1014`	`1014`	`TransactionTreeSetCommitTsData(setts->mainxid, nsubxids, subxids,`
`1015`		`- setts->timestamp, setts->nodeid, true);`
	`1015`	`+ setts->timestamp, setts->nodeid, false);`
`1016`	`1016`	`if (subxids)`
`1017`	`1017`	`pfree(subxids);`
`1018`	`1018`	`}`