Reformat code comment

Discussion: https://www.postgresql.org/message-id/e8f86ba5-48f1-a80a-7f1d-b76bcb9c5c47@2ndquadrant.com

diff --git a/src/backend/access/transam/xlog.c b/src/backend/access/transam/xlog.c
index 3813eadfb49a19351e7836e424583e3a0bece571..b017fd286f2bc3c361595e91548288671aec2d19 100644 (file)
--- a/src/backend/access/transam/xlog.c
+++ b/src/backend/access/transam/xlog.c
@@ -6297,16 +6297,17 @@ StartupXLOG(void)
 
        /*----------
         * If we previously crashed, perform a couple of actions:
-        *      - The pg_wal directory may still include some temporary WAL segments
-        * used when creating a new segment, so perform some clean up to not
-        * bloat this path.  This is done first as there is no point to sync this
-        * temporary data.
-        *      - There might be data which we had written, intending to fsync it,
-        * but which we had not actually fsync'd yet. Therefore, a power failure
-        * in the near future might cause earlier unflushed writes to be lost,
-        * even though more recent data written to disk from here on would be
-        * persisted.  To avoid that, fsync the entire data directory.
-        *---------
+        *
+        * - The pg_wal directory may still include some temporary WAL segments
+        *   used when creating a new segment, so perform some clean up to not
+        *   bloat this path.  This is done first as there is no point to sync
+        *   this temporary data.
+        *
+        * - There might be data which we had written, intending to fsync it, but
+        *   which we had not actually fsync'd yet.  Therefore, a power failure in
+        *   the near future might cause earlier unflushed writes to be lost, even
+        *   though more recent data written to disk from here on would be
+        *   persisted.  To avoid that, fsync the entire data directory.
         */
        if (ControlFile->state != DB_SHUTDOWNED &&
                ControlFile->state != DB_SHUTDOWNED_IN_RECOVERY)