Hi In commit 70e8186 xlog.c was split to move recovery-related code into xlogrecovery.c. Some comments still refer to xlog.c and need to be updated accordingly.
This patch fixes those comments to point to the correct file. Thanks Imran Zaheer
From 4eb0bdf69d077c1061300908ba6a9b29492985b7 Mon Sep 17 00:00:00 2001 From: Imran Zaheer <[email protected]> Date: Thu, 4 Jun 2026 12:56:52 +0500 Subject: [PATCH v1] Update comments to use xlogrecovery.c references Commit 70e8186 split recovery-related code into xlogrecovery.c. Update comments to refer to the correct file. --- src/backend/access/transam/xact.c | 4 ++-- src/backend/access/transam/xlogprefetcher.c | 4 ++-- src/backend/postmaster/startup.c | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/backend/access/transam/xact.c b/src/backend/access/transam/xact.c index 5586fbe5b07..c1d68c4c1c8 100644 --- a/src/backend/access/transam/xact.c +++ b/src/backend/access/transam/xact.c @@ -6223,7 +6223,7 @@ xact_redo_commit(xl_xact_parsed_commit *parsed, * If a transaction completion record arrives that has as-yet * unobserved subtransactions then this will not have been fully * handled by the call to RecordKnownAssignedTransactionIds() in the - * main recovery loop in xlog.c. So we need to do bookkeeping again to + * main recovery loop in xlogrecovery.c. So we need to do bookkeeping again to * cover that case. This is confusing and it is easy to think this * call is irrelevant, which has happened three times in development * already. Leave it in. @@ -6361,7 +6361,7 @@ xact_redo_abort(xl_xact_parsed_abort *parsed, TransactionId xid, * If a transaction completion record arrives that has as-yet * unobserved subtransactions then this will not have been fully * handled by the call to RecordKnownAssignedTransactionIds() in the - * main recovery loop in xlog.c. So we need to do bookkeeping again to + * main recovery loop in xlogrecovery.c. So we need to do bookkeeping again to * cover that case. This is confusing and it is easy to think this * call is irrelevant, which has happened three times in development * already. Leave it in. diff --git a/src/backend/access/transam/xlogprefetcher.c b/src/backend/access/transam/xlogprefetcher.c index 83a3f97a57c..ded482ee406 100644 --- a/src/backend/access/transam/xlogprefetcher.c +++ b/src/backend/access/transam/xlogprefetcher.c @@ -804,9 +804,9 @@ XLogPrefetcherNextBlock(uintptr_t pgsr_private, XLogRecPtr *lsn) /* * Several callsites need to be able to read exactly one record - * without any internal readahead. Examples: xlog.c reading + * without any internal readahead. Examples: xlogrecovery.c reading * checkpoint records with emode set to PANIC, which might otherwise - * cause XLogPageRead() to panic on some future page, and xlog.c + * cause XLogPageRead() to panic on some future page, and xlogrecovery.c * determining where to start writing WAL next, which depends on the * contents of the reader's internal buffer after reading one record. * Therefore, don't even think about prefetching until the first diff --git a/src/backend/postmaster/startup.c b/src/backend/postmaster/startup.c index b46bac681fe..860b9991e76 100644 --- a/src/backend/postmaster/startup.c +++ b/src/backend/postmaster/startup.c @@ -118,7 +118,7 @@ StartupProcShutdownHandler(SIGNAL_ARGS) /* * Re-read the config file. * - * If one of the critical walreceiver options has changed, flag xlog.c + * If one of the critical walreceiver options has changed, flag xlogrecovery.c * to restart it. */ static void -- 2.34.1
