aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execParallel.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-10-22 17:34:32 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-10-22 18:29:46 -0400
commit3dfb1942d9b8748b93094a430289e2f7f3b3ae0d (patch)
treefc5741979ce8e129518f2da8d0bfdd8948444fdf /src/backend/executor/execParallel.c
parent8bb0c9770e80fa79f15b27af8f3c3f2833225aa3 (diff)
downloadpostgresql-3dfb1942d9b8748b93094a430289e2f7f3b3ae0d.tar.gz
postgresql-3dfb1942d9b8748b93094a430289e2f7f3b3ae0d.zip
Avoid premature de-doubling of quote marks in ECPG strings.
If you write the literal 'abc''def' in an EXEC SQL command, that will come out the other end as 'abc'def', triggering a syntax error in the backend. Likewise, "abc""def" is reduced to "abc"def" which is wrong syntax for a quoted identifier. The cause is that the lexer thinks it should emit just one quote mark, whereas what it really should do is keep the string as-is. Add some docs and test cases, too. Although this seems clearly a bug, I fear users wouldn't appreciate changing it in minor releases. Some may well be working around it by applying an extra doubling of affected quotes, as for example sql/dyntest.pgc has been doing. Per investigation of a report from 1250kv, although this isn't exactly what he/she was on about. Discussion: https://postgr.es/m/673825.1603223178@sss.pgh.pa.us
Diffstat (limited to 'src/backend/executor/execParallel.c')
0 files changed, 0 insertions, 0 deletions