Commit 672efc08 authored by Tom Lane's avatar Tom Lane

Update obsolete comment. Noted by Josh Tolley.

parent 7b81782b
...@@ -11,7 +11,7 @@ ...@@ -11,7 +11,7 @@
* Portions Copyright (c) 1996-2010, PostgreSQL Global Development Group * Portions Copyright (c) 1996-2010, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California * 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) ...@@ -227,11 +227,9 @@ XLogCheckInvalidPages(void)
* LockBuffer(buffer, BUFFER_LOCK_EXCLUSIVE), for reading from the main * LockBuffer(buffer, BUFFER_LOCK_EXCLUSIVE), for reading from the main
* fork. * fork.
* *
* (Getting the lock is not really necessary, since we expect that this is * (Getting the buffer lock is not really necessary during single-process
* only used during single-process XLOG replay, but some subroutines such * crash recovery, but some subroutines such as MarkBufferDirty will complain
* as MarkBufferDirty will complain if we don't. And hopefully we'll get * if we don't have the lock. In hot standby mode it's definitely necessary.)
* hot standby support in the future, where there will be backends running
* read-only queries during XLOG replay.)
* *
* The returned buffer is exclusively-locked. * The returned buffer is exclusively-locked.
* *
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment