aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2025-02-10 10:03:40 -0500
committerAndres Freund <andres@anarazel.de>2025-02-10 10:03:40 -0500
commit46ddf98df0517d39108abdf5da29e0cae8d4ebfd (patch)
tree7d1e6bbc9ee180fce3eeefdc66234b57e68d5696 /src/backend/executor/nodeHashjoin.c
parente0ef3d776a349db2c63075241626563b79477bd4 (diff)
downloadpostgresql-46ddf98df0517d39108abdf5da29e0cae8d4ebfd.tar.gz
postgresql-46ddf98df0517d39108abdf5da29e0cae8d4ebfd.zip
Add test of various escape functions
As highlighted by the prior commit, writing correct escape functions is less trivial than one might hope. This test module tries to verify that different escaping functions behave reasonably. It e.g. tests: - Invalidly encoded input to an escape function leads to invalidly encoded output - Trailing incomplete multi-byte characters are handled sensibly - Escaped strings are parsed as single statement by psql's parser (which derives from the backend parser) There are further tests that would be good to add. But even in the current state it was rather useful for writing the fix in the prior commit. Reviewed-by: Noah Misch <noah@leadboat.com> Backpatch-through: 13 Security: CVE-2025-1094
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions