From b985d48779146b7ba969b0963614ad7683589bc8 Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Sun, 20 Nov 2011 23:50:27 -0500
Subject: Further code review for range types patch.

Fix some bugs in coercion logic and pg_dump; more comment cleanup;
minor cosmetic improvements.
---
 src/pl/plpgsql/src/pl_comp.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'src/pl')

diff --git a/src/pl/plpgsql/src/pl_comp.c b/src/pl/plpgsql/src/pl_comp.c
index 04d8b532c3..275cad7b5c 100644
--- a/src/pl/plpgsql/src/pl_comp.c
+++ b/src/pl/plpgsql/src/pl_comp.c
@@ -2378,7 +2378,7 @@ compute_function_hashkey(FunctionCallInfo fcinfo,
 /*
  * This is the same as the standard resolve_polymorphic_argtypes() function,
  * but with a special case for validation: assume that polymorphic arguments
- * are integer, integer-range or integer-array.  Also, we go ahead and report
+ * are integer, integer-array or integer-range.  Also, we go ahead and report
  * the error if we can't resolve the types.
  */
 static void
@@ -2412,12 +2412,12 @@ plpgsql_resolve_polymorphic_argtypes(int numargs,
 				case ANYENUMOID:		/* XXX dubious */
 					argtypes[i] = INT4OID;
 					break;
-				case ANYRANGEOID:
-					argtypes[i] = INT4RANGEOID;
-					break;
 				case ANYARRAYOID:
 					argtypes[i] = INT4ARRAYOID;
 					break;
+				case ANYRANGEOID:
+					argtypes[i] = INT4RANGEOID;
+					break;
 				default:
 					break;
 			}
-- 
cgit v1.2.3