aboutsummaryrefslogtreecommitdiff
path: root/src/include/catalog/pg_control.h
diff options
context:
space:
mode:
Diffstat (limited to 'src/include/catalog/pg_control.h')
-rw-r--r--src/include/catalog/pg_control.h45
1 files changed, 22 insertions, 23 deletions
diff --git a/src/include/catalog/pg_control.h b/src/include/catalog/pg_control.h
index 158a4ee92b4..847ad08b2ef 100644
--- a/src/include/catalog/pg_control.h
+++ b/src/include/catalog/pg_control.h
@@ -8,7 +8,7 @@
* Portions Copyright (c) 1996-2005, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California
*
- * $PostgreSQL: pgsql/src/include/catalog/pg_control.h,v 1.24 2005/10/03 00:28:43 tgl Exp $
+ * $PostgreSQL: pgsql/src/include/catalog/pg_control.h,v 1.25 2005/10/15 02:49:42 momjian Exp $
*
*-------------------------------------------------------------------------
*/
@@ -31,15 +31,14 @@
typedef struct CheckPoint
{
XLogRecPtr redo; /* next RecPtr available when we began to
- * create CheckPoint (i.e. REDO start
- * point) */
+ * create CheckPoint (i.e. REDO start point) */
XLogRecPtr undo; /* first record of oldest in-progress
- * transaction when we started (i.e. UNDO
- * end point) */
+ * transaction when we started (i.e. UNDO end
+ * point) */
TimeLineID ThisTimeLineID; /* current TLI */
TransactionId nextXid; /* next free XID */
Oid nextOid; /* next free OID */
- MultiXactId nextMulti; /* next free MultiXactId */
+ MultiXactId nextMulti; /* next free MultiXactId */
MultiXactOffset nextMultiOffset; /* next free MultiXact offset */
time_t time; /* time stamp of checkpoint */
} CheckPoint;
@@ -74,23 +73,23 @@ typedef enum DBState
typedef struct ControlFileData
{
/*
- * Unique system identifier --- to ensure we match up xlog files with
- * the installation that produced them.
+ * Unique system identifier --- to ensure we match up xlog files with the
+ * installation that produced them.
*/
uint64 system_identifier;
/*
* Version identifier information. Keep these fields at the same offset,
- * especially pg_control_version; they won't be real useful if they
- * move around. (For historical reasons they must be 8 bytes into
- * the file rather than immediately at the front.)
+ * especially pg_control_version; they won't be real useful if they move
+ * around. (For historical reasons they must be 8 bytes into the file
+ * rather than immediately at the front.)
*
* pg_control_version identifies the format of pg_control itself.
* catalog_version_no identifies the format of the system catalogs.
*
- * There are additional version identifiers in individual files; for
- * example, WAL logs contain per-page magic numbers that can serve as
- * version cues for the WAL log.
+ * There are additional version identifiers in individual files; for example,
+ * WAL logs contain per-page magic numbers that can serve as version cues
+ * for the WAL log.
*/
uint32 pg_control_version; /* PG_CONTROL_VERSION */
uint32 catalog_version_no; /* see catversion.h */
@@ -108,13 +107,13 @@ typedef struct ControlFileData
CheckPoint checkPointCopy; /* copy of last check point record */
/*
- * This data is used to check for hardware-architecture compatibility
- * of the database and the backend executable. We need not check
- * endianness explicitly, since the pg_control version will surely
- * look wrong to a machine of different endianness, but we do need
- * to worry about MAXALIGN and floating-point format. (Note: storage
- * layout nominally also depends on SHORTALIGN and INTALIGN, but in
- * practice these are the same on all architectures of interest.)
+ * This data is used to check for hardware-architecture compatibility of
+ * the database and the backend executable. We need not check endianness
+ * explicitly, since the pg_control version will surely look wrong to a
+ * machine of different endianness, but we do need to worry about MAXALIGN
+ * and floating-point format. (Note: storage layout nominally also
+ * depends on SHORTALIGN and INTALIGN, but in practice these are the same
+ * on all architectures of interest.)
*
* Testing just one double value is not a very bulletproof test for
* floating-point compatibility, but it will catch most cases.
@@ -124,8 +123,8 @@ typedef struct ControlFileData
#define FLOATFORMAT_VALUE 1234567.0
/*
- * This data is used to make sure that configuration of this database
- * is compatible with the backend executable.
+ * This data is used to make sure that configuration of this database is
+ * compatible with the backend executable.
*/
uint32 blcksz; /* block size for this DB */
uint32 relseg_size; /* blocks per segment of large relation */