pgindent run over code.

src/backend/utils/error/elog.c

@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/error/elog.c,v 1.44 1999/05/10 00:46:11 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/error/elog.c,v 1.45 1999/05/25 16:12:24 momjian Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -55,7 +55,7 @@ static int	Err_file = -1;
 static int	ElogDebugIndentLevel = 0;
 
 /*
- * elog 
+ * elog
  *		Old error logging function.
  */
 void
@@ -167,7 +167,7 @@ elog(int lev, const char *fmt,...)
 	 * front-end program, write to it first.  This is important because
 	 * there's a bug in the socket code on ultrix.  If the front end has
 	 * gone away (so the channel to it has been closed at the other end),
-	 * then writing here can cause this backend to exit without warning 
+	 * then writing here can cause this backend to exit without warning
 	 * that is, write() does an exit(). In this case, our only hope of
 	 * finding out what's going on is if Err_file was set to some disk
 	 * log.  This is a major pain.
@@ -190,26 +190,32 @@ elog(int lev, const char *fmt,...)
 	if (IsUnderPostmaster && lev > DEBUG)
 	{
 		/* notices are not errors, handle 'em differently */
-		char msgtype;
+		char		msgtype;
+
 		if (lev == NOTICE)
 			msgtype = 'N';
 		else
 		{
-			/* Abort any COPY OUT in progress when an error is detected.
-			 * This hack is necessary because of poor design of copy protocol.
+
+			/*
+			 * Abort any COPY OUT in progress when an error is detected.
+			 * This hack is necessary because of poor design of copy
+			 * protocol.
 			 */
 			pq_endcopyout(true);
 			msgtype = 'E';
 		}
 		/* exclude the timestamp from msg sent to frontend */
 		pq_puttextmessage(msgtype, line + TIMESTAMP_SIZE);
+
 		/*
 		 * This flush is normally not necessary, since postgres.c will
 		 * flush out waiting data when control returns to the main loop.
 		 * But it seems best to leave it here, so that the client has some
-		 * clue what happened if the backend dies before getting back to the
-		 * main loop ... error/notice messages should not be a performance-
-		 * critical path anyway, so an extra flush won't hurt much ...
+		 * clue what happened if the backend dies before getting back to
+		 * the main loop ... error/notice messages should not be a
+		 * performance- critical path anyway, so an extra flush won't hurt
+		 * much ...
 		 */
 		pq_flush();
 	}

src/backend/utils/error/exc.c

@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/exc.c,v 1.24 1999/02/13 23:19:48 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/exc.c,v 1.25 1999/05/25 16:12:26 momjian Exp $
  *
  * NOTE
  *	  XXX this code needs improvement--check for state violations and
@@ -48,7 +48,7 @@ extern char *ProgramName;
  */
 
 /*
- * EnableExceptionHandling 
+ * EnableExceptionHandling
  *		Enables/disables the exception handling system.
  *
  * Note:

src/backend/utils/error/excid.c

@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/excid.c,v 1.5 1999/02/13 23:19:48 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/excid.c,v 1.6 1999/05/25 16:12:26 momjian Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -22,19 +22,19 @@
 
 
 /*
- * FailedAssertion 
+ * FailedAssertion
  *		Indicates an Assert(...) failed.
  */
 Exception	FailedAssertion = {"Failed Assertion"};
 
 /*
- * BadState 
+ * BadState
  *		Indicates a function call request is inconsistent with module state.
  */
 Exception	BadState = {"Bad State for Function Call"};
 
 /*
- * BadArg 
+ * BadArg
  *		Indicates a function call argument or arguments is out-of-bounds.
  */
 Exception	BadArg = {"Bad Argument to Function Call"};
@@ -44,19 +44,19 @@ Exception	BadArg = {"Bad Argument to Function Call"};
  *****************************************************************************/
 
 /*
- * BadAllocSize 
+ * BadAllocSize
  *		Indicates that an allocation request is of unreasonable size.
  */
 Exception	BadAllocSize = {"Too Large Allocation Request"};
 
 /*
- * ExhaustedMemory 
+ * ExhaustedMemory
  *		Indicates an dynamic memory allocation failed.
  */
 Exception	ExhaustedMemory = {"Memory Allocation Failed"};
 
 /*
- * Unimplemented 
+ * Unimplemented
  *		Indicates a function call request requires unimplemented code.
  */
 Exception	Unimplemented = {"Unimplemented Functionality"};

src/backend/utils/error/format.c

@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/format.c,v 1.10 1999/02/13 23:19:49 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/error/Attic/format.c,v 1.11 1999/05/25 16:12:26 momjian Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -29,6 +29,7 @@ char *
 form(const char *fmt,...)
 {
 	va_list		args;
+
 	va_start(args, fmt);
 	vsnprintf(FormBuf, FormMaxSize - 1, fmt, args);
 	va_end(args);