Fix incorrect comments.
authorRobert Haas <rhaas@postgresql.org>
Mon, 6 Mar 2017 18:10:55 +0000 (13:10 -0500)
committerRobert Haas <rhaas@postgresql.org>
Mon, 6 Mar 2017 18:11:49 +0000 (13:11 -0500)
Commit 19dc233c32f2900e57b8da4f41c0f662ab42e080 introduced these
comments.  Michael Paquier noticed that one of them had a typo, but
a bigger problem is that they were not an accurate description of
what the code was doing.

Patch by me.

src/backend/utils/adt/misc.c

index ff6a25d2b60233a356afb60616443bd67fd8f8f2..869c3bd7fa52440fedf4524e1d81ccfbd9e79e57 100644 (file)
@@ -939,10 +939,7 @@ pg_current_logfile(PG_FUNCTION_ARGS)
        log_filepath = strchr(lbuffer, ' ');
        if (log_filepath == NULL)
        {
-           /*
-            * No space found, file content is corrupted.  Return NULL to the
-            * caller and inform him on the situation.
-            */
+           /* Uh oh.  No newline found, so file content is corrupted. */
            elog(ERROR,
                 "missing space character in \"%s\"", LOG_METAINFO_DATAFILE);
            break;
@@ -953,10 +950,7 @@ pg_current_logfile(PG_FUNCTION_ARGS)
        nlpos = strchr(log_filepath, '\n');
        if (nlpos == NULL)
        {
-           /*
-            * No newlinei found, file content is corrupted.  Return NULL to
-            * the caller and inform him on the situation.
-            */
+           /* Uh oh.  No newline found, so file content is corrupted. */
            elog(ERROR,
               "missing newline character in \"%s\"", LOG_METAINFO_DATAFILE);
            break;