>From 9fa69ccc79c7bc42be554bc3f4e740c4e77d50d7 Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Sat, 14 Sep 2013 23:15:10 +0200 Subject: [PATCH] Allow custom GUCs to be nested more than one level in config files Doing so was allowed via SET, postgres -c and set_config() before. Allowing to do so is useful for grouping together variables inside an extension's toplevel namespace. There still are differences in the accepted variable names between the different methods of setting GUCs after this commit, but the concensus is that those are acceptable. --- src/backend/utils/misc/guc-file.l | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/utils/misc/guc-file.l b/src/backend/utils/misc/guc-file.l index b730a12..ff4202d 100644 --- a/src/backend/utils/misc/guc-file.l +++ b/src/backend/utils/misc/guc-file.l @@ -78,7 +78,7 @@ LETTER [A-Za-z_\200-\377] LETTER_OR_DIGIT [A-Za-z_0-9\200-\377] ID {LETTER}{LETTER_OR_DIGIT}* -QUALIFIED_ID {ID}"."{ID} +QUALIFIED_ID {ID}("."{ID})+ UNQUOTED_STRING {LETTER}({LETTER_OR_DIGIT}|[-._:/])* STRING \'([^'\\\n]|\\.|\'\')*\' -- 1.8.4.21.g992c386.dirty