forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commitdb37ab2
committed
Fix pgbench lexer's "continuation" rule to cope with Windows newlines.
Our general practice in frontend code is to accept input with eitherUnix-style newlines (\n) or DOS-style (\r\n). pgbench was mostly downwith that, but its rule for line continuations (backslash-newline) wasnot. This had been masked on Windows buildfarm machines before commit0ba06e0 by use of Windows text mode to read files. We could have fixedit by forcing text mode again, but it's better to fix the parsing codeso 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.us1 parentf9907c6 commitdb37ab2
1 file changed
+7
-3
lines changedLines changed: 7 additions & 3 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
69 | 69 |
| |
70 | 70 |
| |
71 | 71 |
| |
72 |
| - | |
| 72 | + | |
73 | 73 |
| |
74 | 74 |
| |
75 | 75 |
| |
| |||
122 | 122 |
| |
123 | 123 |
| |
124 | 124 |
| |
125 |
| - | |
126 |
| - | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
| 130 | + | |
127 | 131 |
| |
128 | 132 |
| |
129 | 133 |
| |
|
0 commit comments
Comments
(0)