Post-PG 10 beta1 pgindent run

perltidy run not included.

1 files changed, 10 insertions, 8 deletions

diff --git a/src/backend/replication/logical/logicalfuncs.c b/src/backend/replication/logical/logicalfuncs.c
index 27164de093d..ba4d8cc5a45 100644
--- a/src/backend/replication/logical/logicalfuncs.c
+++ b/src/backend/replication/logical/logicalfuncs.c
@@ -328,17 +328,19 @@ pg_logical_slot_get_changes_guts(FunctionCallInfo fcinfo, bool confirm, bool bin
 		if (ctx->reader->EndRecPtr != InvalidXLogRecPtr && confirm)
 		{
 			LogicalConfirmReceivedLocation(ctx->reader->EndRecPtr);
+
 			/*
 			 * If only the confirmed_flush_lsn has changed the slot won't get
-			 * marked as dirty by the above. Callers on the walsender interface
-			 * are expected to keep track of their own progress and don't need
-			 * it written out. But SQL-interface users cannot specify their own
-			 * start positions and it's harder for them to keep track of their
-			 * progress, so we should make more of an effort to save it for them.
+			 * marked as dirty by the above. Callers on the walsender
+			 * interface are expected to keep track of their own progress and
+			 * don't need it written out. But SQL-interface users cannot
+			 * specify their own start positions and it's harder for them to
+			 * keep track of their progress, so we should make more of an
+			 * effort to save it for them.
 			 *
-			 * Dirty the slot so it's written out at the next checkpoint. We'll
-			 * still lose its position on crash, as documented, but it's better
-			 * than always losing the position even on clean restart.
+			 * Dirty the slot so it's written out at the next checkpoint.
+			 * We'll still lose its position on crash, as documented, but it's
+			 * better than always losing the position even on clean restart.
 			 */
 			ReplicationSlotMarkDirty();
 		}