Pgindent run before 9.1 beta2.

[postgresql] / src / backend / optimizer / path / costsize.c

diff --git a/src/backend/optimizer/path/costsize.c b/src/backend/optimizer/path/costsize.c
index c4404b1bd1712548071d1d7b80b72e65dd45d77b..bb38768bd4358f72896e2d2c549bbd64dedcd24d 100644 (file)
--- a/src/backend/optimizer/path/costsize.c
+++ b/src/backend/optimizer/path/costsize.c
@@ -2687,7 +2687,7 @@ cost_qual_eval_walker(Node *node, cost_qual_eval_context *context)
         * evaluation of AND/OR?  Probably *not*, because that would make the
         * results depend on the clause ordering, and we are not in any position
         * to expect that the current ordering of the clauses is the one that's
-        * going to end up being used.  The above per-RestrictInfo caching would
+        * going to end up being used.  The above per-RestrictInfo caching would
         * not mix well with trying to re-order clauses anyway.
         */
        if (IsA(node, FuncExpr))