Tom Lane db37ab2c60 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		2018-09-17 12:11:43 -04:00
..
t	Fix handling of pgbench's hash when no argument is provided	2018-07-27 13:40:24 +09:00
.gitignore	Call xlc __isync() after, not before, associated compare-and-swap.	2016-02-19 22:47:50 -05:00
exprparse.y	Fix handling of pgbench's hash when no argument is provided	2018-07-27 13:40:24 +09:00
exprscan.l	Fix pgbench lexer's "continuation" rule to cope with Windows newlines.	2018-09-17 12:11:43 -04:00
Makefile	Prevent accidental linking of system-supplied copies of libpq.so etc.	2018-04-03 16:26:05 -04:00
pgbench.c	doc: Update redirecting links	2018-07-16 10:48:05 +02:00
pgbench.h	Add general purpose hasing functions to pgbench.	2018-03-21 18:01:23 +03:00