diff options
| author | Tom Lane | 2022-01-24 17:09:46 +0000 |
|---|---|---|
| committer | Tom Lane | 2022-01-24 17:09:46 +0000 |
| commit | 449a696236ff6d8a86b98ae6503aa51dc39a37b2 (patch) | |
| tree | f4ac4871439d1c320680461392171a9f17ff2c9a | |
| parent | bd110e250e9d9291d7fc1ea12ddd5d177a2460bd (diff) | |
Remember to reset yy_start state when firing up repl_scanner.l.
Without this, we get odd behavior when the previous cycle of
lexing exited in a non-default exclusive state. Every other
copy of this code is aware that it has to do BEGIN(INITIAL),
but repl_scanner.l did not get that memo.
The real-world impact of this is probably limited, since most
replication clients would abandon their connection after getting
a syntax error. Still, it's a bug.
This mistake is old, so back-patch to all supported branches.
Discussion: https://postgr.es/m/1874781.1643035952@sss.pgh.pa.us
| -rw-r--r-- | src/backend/replication/repl_scanner.l | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/backend/replication/repl_scanner.l b/src/backend/replication/repl_scanner.l index 7bb501f5949..f602c5991fa 100644 --- a/src/backend/replication/repl_scanner.l +++ b/src/backend/replication/repl_scanner.l @@ -243,6 +243,9 @@ replication_scanner_init(const char *str) memcpy(scanbuf, str, slen); scanbuf[slen] = scanbuf[slen + 1] = YY_END_OF_BUFFER_CHAR; scanbufhandle = yy_scan_buffer(scanbuf, slen + 2); + + /* Make sure we start in proper state */ + BEGIN(INITIAL); } void |