From 672efc08654e5744b42d2809f903cb7528898620 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 8 Jul 2010 16:08:30 +0000 Subject: [PATCH] Update obsolete comment. Noted by Josh Tolley. --- src/backend/access/transam/xlogutils.c | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/src/backend/access/transam/xlogutils.c b/src/backend/access/transam/xlogutils.c index af6a0d29e8..3d7c7cf69e 100644 --- a/src/backend/access/transam/xlogutils.c +++ b/src/backend/access/transam/xlogutils.c @@ -11,7 +11,7 @@ * Portions Copyright (c) 1996-2010, PostgreSQL Global Development Group * Portions Copyright (c) 1994, Regents of the University of California * - * $PostgreSQL: pgsql/src/backend/access/transam/xlogutils.c,v 1.70 2010/02/09 21:43:29 tgl Exp $ + * $PostgreSQL: pgsql/src/backend/access/transam/xlogutils.c,v 1.71 2010/07/08 16:08:30 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -227,11 +227,9 @@ XLogCheckInvalidPages(void) * LockBuffer(buffer, BUFFER_LOCK_EXCLUSIVE), for reading from the main * fork. * - * (Getting the lock is not really necessary, since we expect that this is - * only used during single-process XLOG replay, but some subroutines such - * as MarkBufferDirty will complain if we don't. And hopefully we'll get - * hot standby support in the future, where there will be backends running - * read-only queries during XLOG replay.) + * (Getting the buffer lock is not really necessary during single-process + * crash recovery, but some subroutines such as MarkBufferDirty will complain + * if we don't have the lock. In hot standby mode it's definitely necessary.) * * The returned buffer is exclusively-locked. *