aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.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
commitef9706bbc8ce917a366e4640df8c603c9605817a (patch)
treec77149b79355c4aa6f89d5784b8896c0c16c0d7c /contrib/postgres_fdw/postgres_fdw.c
parent1042de69dbb6f3c0aa92a741a68aeca23f4ed45e (diff)
downloadpostgresql-ef9706bbc8ce917a366e4640df8c603c9605817a.tar.gz
postgresql-ef9706bbc8ce917a366e4640df8c603c9605817a.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 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions