@@ -6297,16 +6297,17 @@ StartupXLOG(void)
62976297
62986298/*----------
62996299 * If we previously crashed, perform a couple of actions:
6300- *- The pg_wal directory may still include some temporary WAL segments
6301- * used when creating a new segment, so perform some clean up to not
6302- * bloat this path. This is done first as there is no point to sync this
6303- * temporary data.
6304- *- There might be data which we had written, intending to fsync it,
6305- * but which we had not actually fsync'd yet. Therefore, a power failure
6306- * in the near future might cause earlier unflushed writes to be lost,
6307- * even though more recent data written to disk from here on would be
6308- * persisted. To avoid that, fsync the entire data directory.
6309- *---------
6300+ *
6301+ * - The pg_wal directory may still include some temporary WAL segments
6302+ * used when creating a new segment, so perform some clean up to not
6303+ * bloat this path. This is done first as there is no point to sync
6304+ * this temporary data.
6305+ *
6306+ * - There might be data which we had written, intending to fsync it, but
6307+ * which we had not actually fsync'd yet. Therefore, a power failure in
6308+ * the near future might cause earlier unflushed writes to be lost, even
6309+ * though more recent data written to disk from here on would be
6310+ * persisted. To avoid that, fsync the entire data directory.
63106311 */
63116312if (ControlFile -> state != DB_SHUTDOWNED &&
63126313ControlFile -> state != DB_SHUTDOWNED_IN_RECOVERY )