diff options
author | Andres Freund <andres@anarazel.de> | 2025-02-10 10:03:38 -0500 |
---|---|---|
committer | Andres Freund <andres@anarazel.de> | 2025-02-10 10:03:38 -0500 |
commit | 7d43ca6fe068015b403ffa1762f4df4efdf68b69 (patch) | |
tree | f202986c86d1b29ab3d3b2c3ddf1b6c1b63516d7 /src/fe_utils/string_utils.c | |
parent | 439776ba64d9ad8c47293568cd6d2930c6d5218a (diff) | |
download | postgresql-7d43ca6fe068015b403ffa1762f4df4efdf68b69.tar.gz postgresql-7d43ca6fe068015b403ffa1762f4df4efdf68b69.zip |
Add pg_encoding_set_invalid()
There are cases where we cannot / do not want to error out for invalidly
encoded input. In such cases it can be useful to replace e.g. an incomplete
multi-byte characters with bytes that will trigger an error when getting
validated as part of a larger string.
Unfortunately, until now, for some encoding no such sequence existed. For
those encodings this commit removes one previously accepted input combination
- we consider that to be ok, as the chosen bytes are outside of the valid
ranges for the encodings, we just previously failed to detect that.
As we cannot add a new field to pg_wchar_table without breaking ABI, this is
implemented "in-line" in the newly added function.
Author: Noah Misch <noah@leadboat.com>
Reviewed-by: Andres Freund <andres@anarazel.de>
Backpatch-through: 13
Security: CVE-2025-1094
Diffstat (limited to 'src/fe_utils/string_utils.c')
0 files changed, 0 insertions, 0 deletions