aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/dbcommands.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-01-24 12:09:46 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-01-24 12:09:46 -0500
commit3c06ec6d1412a6ebf05ee0566b5c05969f0b541f (patch)
tree484aa12cfbc481fa54705c5687ddfee258e69c09 /src/backend/commands/dbcommands.c
parentf032f63e727c1ab07603b3d1cd88d50f850d5738 (diff)
downloadpostgresql-3c06ec6d1412a6ebf05ee0566b5c05969f0b541f.tar.gz
postgresql-3c06ec6d1412a6ebf05ee0566b5c05969f0b541f.zip
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
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions