From 0c985ab5a86b4ca9d8e312bfd0db5536b2be121e Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 26 Jun 2003 18:23:07 +0000 Subject: [PATCH] Add comment pointing out that XLByteToPrevSeg macro is not broken. --- src/backend/access/transam/xlog.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c index 7fa274922b0..47232fe5ce1 100644 --- a/src/backend/access/transam/xlog.c +++ b/src/backend/access/transam/xlog.c @@ -7,7 +7,7 @@ * Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group * Portions Copyright (c) 1994, Regents of the University of California * - * $Header: /cvsroot/pgsql/src/backend/access/transam/xlog.c,v 1.116 2003/05/22 14:39:28 tgl Exp $ + * $Header: /cvsroot/pgsql/src/backend/access/transam/xlog.c,v 1.117 2003/06/26 18:23:07 tgl Exp $ * *------------------------------------------------------------------------- */ @@ -347,7 +347,8 @@ static ControlFileData *ControlFile = NULL; * For XLByteToSeg, do the computation at face value. For XLByteToPrevSeg, * a boundary byte is taken to be in the previous segment. This is suitable * for deciding which segment to write given a pointer to a record end, - * for example. + * for example. (We can assume xrecoff is not zero, since no valid recptr + * can have that.) */ #define XLByteToSeg(xlrp, logId, logSeg) \ ( logId = (xlrp).xlogid, \