@@ -91,7 +91,7 @@ struct XidCache
91
91
#define INVALID_PGPROCNO PG_INT32_MAX
92
92
93
93
/*
94
- * Flags for PGPROC.delayChkpt
94
+ * Flags for PGPROC.delayChkptFlags
95
95
*
96
96
* These flags can be used to delay the start or completion of a checkpoint
97
97
* for short periods. A flag is in effect if the corresponding bit is set in
@@ -118,7 +118,7 @@ struct XidCache
118
118
* to phase 3. This is useful if we are performing a WAL-logged operation that
119
119
* might invalidate buffers, such as relation truncation. In this case, we need
120
120
* to ensure that any buffers which were invalidated and thus not flushed by
121
- * the checkpoint are actaully destroyed on disk. Replay can cope with a file
121
+ * the checkpoint are actually destroyed on disk. Replay can cope with a file
122
122
* or block that doesn't exist, but not with a block that has the wrong
123
123
* contents.
124
124
*/
@@ -149,7 +149,7 @@ typedef enum
149
149
* but its myProcLocks[] lists are valid.
150
150
*
151
151
* We allow many fields of this struct to be accessed without locks, such as
152
- * delayChkpt and isBackgroundWorker. However, keep in mind that writing
152
+ * delayChkptFlags and isBackgroundWorker. However, keep in mind that writing
153
153
* mirrored ones (see below) requires holding ProcArrayLock or XidGenLock in
154
154
* at least shared mode, so that pgxactoff does not change concurrently.
155
155
*
0 commit comments