From 3e9df858f0de5f1a37c71f24373caf8c870f6993 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 21 Jun 2016 20:23:20 -0400 Subject: [PATCH] Update comment about allowing GUCs to change scanning. Reported-by: David G. Johnston Discussion: CAKFQuwZZvnxwSq9tNtvL+uyuDKGgV91zR_agtPxQHRWMWQRP8g@mail.gmail.com --- src/backend/parser/scan.l | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/backend/parser/scan.l b/src/backend/parser/scan.l index 4d905e6b94..998349d742 100644 --- a/src/backend/parser/scan.l +++ b/src/backend/parser/scan.l @@ -55,8 +55,7 @@ fprintf_to_ereport(const char *fmt, const char *msg) * GUC variables. This is a DIRECT violation of the warning given at the * head of gram.y, ie flex/bison code must not depend on any GUC variables; * as such, changing their values can induce very unintuitive behavior. - * But we shall have to live with it as a short-term thing until the switch - * to SQL-standard string syntax is complete. + * But we shall have to live with it until we can remove these variables. */ int backslash_quote = BACKSLASH_QUOTE_SAFE_ENCODING; bool escape_string_warning = true; -- 2.40.0