Run pgindent on 9.2 source tree in preparation for first 9.3

commit-fest.

1 files changed, 5 insertions, 5 deletions

diff --git a/src/backend/utils/time/tqual.c b/src/backend/utils/time/tqual.c
index 01f73980aff..4caef9ca25e 100644
--- a/src/backend/utils/time/tqual.c
+++ b/src/backend/utils/time/tqual.c
@@ -1226,7 +1226,7 @@ HeapTupleSatisfiesVacuum(HeapTupleHeader tuple, TransactionId OldestXmin,
  *	in lieu of HeapTupleSatisifesVacuum when the tuple has just been
  *	tested by HeapTupleSatisfiesMVCC and, therefore, any hint bits that
  *	can be set should already be set.  We assume that if no hint bits
- *	either for xmin or xmax, the transaction is still running.  This is
+ *	either for xmin or xmax, the transaction is still running.	This is
  *	therefore faster than HeapTupleSatisfiesVacuum, because we don't
  *	consult CLOG (and also because we don't need to give an exact answer,
  *	just whether or not the tuple is surely dead).
@@ -1235,10 +1235,10 @@ bool
 HeapTupleIsSurelyDead(HeapTupleHeader tuple, TransactionId OldestXmin)
 {
 	/*
-	 * If the inserting transaction is marked invalid, then it aborted,
-	 * and the tuple is definitely dead.  If it's marked neither committed
-	 * nor invalid, then we assume it's still alive (since the presumption
-	 * is that all relevant hint bits were just set moments ago).
+	 * If the inserting transaction is marked invalid, then it aborted, and
+	 * the tuple is definitely dead.  If it's marked neither committed nor
+	 * invalid, then we assume it's still alive (since the presumption is that
+	 * all relevant hint bits were just set moments ago).
 	 */
 	if (!(tuple->t_infomask & HEAP_XMIN_COMMITTED))
 		return (tuple->t_infomask & HEAP_XMIN_INVALID) != 0 ? true : false;