pgsql: Remember to reset yy_start state when firing up repl_scanner.l. - Mailing list pgsql-committers

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

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c94c6612da573d2789855b77a47da45a4a19cfbd

Modified Files
--------------
src/backend/replication/repl_scanner.l | 3 +++
1 file changed, 3 insertions(+)