From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon, 17 Sep 2018 16:11:43 +0000 (-0400)
Subject: Fix pgbench lexer's "continuation" rule to cope with Windows newlines.
X-Git-Tag: REL_12_BETA1~1558
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=db37ab2c60b877b977f531bcd680848ee4511537;p=postgresql

Fix pgbench lexer's "continuation" rule to cope with Windows newlines.

Our general practice in frontend code is to accept input with either
Unix-style newlines (\n) or DOS-style (\r\n).  pgbench was mostly down
with that, but its rule for line continuations (backslash-newline) was
not.  This had been masked on Windows buildfarm machines before commit
0ba06e0bf by use of Windows text mode to read files.  We could have fixed
it by forcing text mode again, but it's better to fix the parsing code
so that Windows-style text files on Unix systems don't cause problems.

Back-patch to v10 where pgbench grew line continuations.

Discussion: https://postgr.es/m/17194.1537191697@sss.pgh.pa.us
---

diff --git a/src/bin/pgbench/exprscan.l b/src/bin/pgbench/exprscan.l
index 5c1bd88128..61c20364ed 100644
--- a/src/bin/pgbench/exprscan.l
+++ b/src/bin/pgbench/exprscan.l
@@ -69,7 +69,7 @@ nonspace		[^ \t\r\f\v\n]
 newline			[\n]
 
 /* Line continuation marker */
-continuation	\\{newline}
+continuation	\\\r?{newline}
 
 /* case insensitive keywords */
 and				[Aa][Nn][Dd]
@@ -122,8 +122,12 @@ notnull			[Nn][Oo][Tt][Nn][Uu][Ll][Ll]
 	 * a continuation marker just after a word:
 	 */
 {nonspace}+{continuation}	{
-					/* Found "word\\\n", emit and return just "word" */
-					psqlscan_emit(cur_state, yytext, yyleng - 2);
+					/* Found "word\\\r?\n", emit and return just "word" */
+					int		wordlen = yyleng - 2;
+					if (yytext[wordlen] == '\r')
+						wordlen--;
+					Assert(yytext[wordlen] == '\\');
+					psqlscan_emit(cur_state, yytext, wordlen);
 					return 1;
 				}