Remove the definition for set_name_needs_quotes() on the assumption that

 it is now obsolete. Need some regression test cases to prove otherwise...

diff --git a/src/backend/parser/gram.y b/src/backend/parser/gram.y
index 91e33573aedce76ef0e9282467fd003011d7832b..cc4cb59aae4c416bad73c1038250181e628158fe 100644 (file)
--- a/src/backend/parser/gram.y
+++ b/src/backend/parser/gram.y
@@ -11,7 +11,7 @@
  *
  *
  * IDENTIFICATION
- *   $Header: /cvsroot/pgsql/src/backend/parser/gram.y,v 2.307 2002/04/21 19:21:49 thomas Exp $
+ *   $Header: /cvsroot/pgsql/src/backend/parser/gram.y,v 2.308 2002/04/21 21:37:03 thomas Exp $
  *
  * HISTORY
  *   AUTHOR            DATE            MAJOR EVENT
@@ -6676,25 +6676,3 @@ doNegateFloat(Value *v)
        v->val.str = newval;
    }
 }
-
-/*
- * Decide whether to put double quotes around a name appearing in a SET
- * name_list.  Presently, do so if the name contains whitespace, commas,
- * or uppercase characters.  (This is correct assuming that the result
- * will be deparsed by SplitIdentifierString or similar logic.)
- */
-static bool
-set_name_needs_quotes(const char *name)
-{
-   if (*name == '\0')
-       return true;            /* empty name does need quotes */
-   while (*name)
-   {
-       if (*name == ',' ||
-           isspace((unsigned char) *name) ||
-           isupper((unsigned char) *name))
-           return true;
-       name++;
-   }
-   return false;
-}