From f97a028d8ee3e7d64a93285707af94b612c47651 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Tue, 14 Mar 2017 11:38:30 -0400 Subject: Spelling fixes in code comments From: Josh Soref --- src/backend/parser/parse_collate.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/parser/parse_collate.c') diff --git a/src/backend/parser/parse_collate.c b/src/backend/parser/parse_collate.c index 52ac7227909..cc235d422f5 100644 --- a/src/backend/parser/parse_collate.c +++ b/src/backend/parser/parse_collate.c @@ -802,7 +802,7 @@ merge_collation_state(Oid collation, else if (collation != DEFAULT_COLLATION_OID) { /* - * Ooops, we have a conflict. We cannot throw error + * Oops, we have a conflict. We cannot throw error * here, since the conflict could be resolved by a * later sibling CollateExpr, or the parent might not * care about collation anyway. Return enough info to @@ -821,7 +821,7 @@ merge_collation_state(Oid collation, if (collation != context->collation) { /* - * Ooops, we have a conflict of explicit COLLATE clauses. + * Oops, we have a conflict of explicit COLLATE clauses. * Here we choose to throw error immediately; that is what * the SQL standard says to do, and there's no good reason * to be less strict. -- cgit v1.2.3