]> git.ipfire.org Git - thirdparty/postgresql.git/commitdiff
Disable commit timestamps during bootstrap REL_14_STABLE github/REL_14_STABLE
authorMichael Paquier <michael@paquier.xyz>
Fri, 4 Jul 2025 06:10:24 +0000 (15:10 +0900)
committerMichael Paquier <michael@paquier.xyz>
Fri, 4 Jul 2025 06:10:24 +0000 (15:10 +0900)
Attempting to use commit timestamps during bootstrapping leads to an
assertion failure, that can be reached for example with an initdb -c
that enables track_commit_timestamp.  It makes little sense to register
a commit timestamp for a BootstrapTransactionId, so let's disable the
activation of the module in this case.

This problem has been independently reported once by each author of this
commit.  Each author has proposed basically the same patch, relying on
IsBootstrapProcessingMode() to skip the use of commit_ts during
bootstrap.  The test addition is a suggestion by me, and is applied down
to v16.

Author: Hayato Kuroda <kuroda.hayato@fujitsu.com>
Author: Andy Fan <zhihuifan1213@163.com>
Reviewed-by: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@oss.nttdata.com>
Reviewed-by: Michael Paquier <michael@paquier.xyz>
Discussion: https://postgr.es/m/OSCPR01MB14966FF9E4C4145F37B937E52F5102@OSCPR01MB14966.jpnprd01.prod.outlook.com
Discussion: https://postgr.es/m/87plejmnpy.fsf@163.com
Backpatch-through: 13

src/backend/access/transam/commit_ts.c

index edbe3cf6b5503ed6ad5c81f393622c6b4acb53f7..030bb7cf586090c3d9e2f23226c15e0df8d809aa 100644 (file)
@@ -682,6 +682,13 @@ ActivateCommitTs(void)
        TransactionId xid;
        int                     pageno;
 
+       /*
+        * During bootstrap, we should not register commit timestamps so skip the
+        * activation in this case.
+        */
+       if (IsBootstrapProcessingMode())
+               return;
+
        /* If we've done this already, there's nothing to do */
        LWLockAcquire(CommitTsLock, LW_EXCLUSIVE);
        if (commitTsShared->commitTsActive)