Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit0c985ab

Browse files
committed
Add comment pointing out that XLByteToPrevSeg macro is not broken.
1 parent4505653 commit0c985ab

File tree

1 file changed

+3
-2
lines changed
  • src/backend/access/transam

1 file changed

+3
-2
lines changed

‎src/backend/access/transam/xlog.c

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
* Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group
88
* Portions Copyright (c) 1994, Regents of the University of California
99
*
10-
* $Header: /cvsroot/pgsql/src/backend/access/transam/xlog.c,v 1.116 2003/05/22 14:39:28 tgl Exp $
10+
* $Header: /cvsroot/pgsql/src/backend/access/transam/xlog.c,v 1.117 2003/06/26 18:23:07 tgl Exp $
1111
*
1212
*-------------------------------------------------------------------------
1313
*/
@@ -347,7 +347,8 @@ static ControlFileData *ControlFile = NULL;
347347
* For XLByteToSeg, do the computation at face value. For XLByteToPrevSeg,
348348
* a boundary byte is taken to be in the previous segment.This is suitable
349349
* for deciding which segment to write given a pointer to a record end,
350-
* for example.
350+
* for example. (We can assume xrecoff is not zero, since no valid recptr
351+
* can have that.)
351352
*/
352353
#defineXLByteToSeg(xlrp,logId,logSeg)\
353354
( logId = (xlrp).xlogid, \

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp