mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-13 22:59:31 +02:00
c61a2f5841
characters in all cases. Formerly we mostly just threw warnings for invalid input, and failed to detect it at all if no encoding conversion was required. The tighter check is needed to defend against SQL-injection attacks as per CVE-2006-2313 (further details will be published after release). Embedded zero (null) bytes will be rejected as well. The checks are applied during input to the backend (receipt from client or COPY IN), so it no longer seems necessary to check in textin() and related routines; any string arriving at those functions will already have been validated. Conversion failure reporting (for characters with no equivalent in the destination encoding) has been cleaned up and made consistent while at it. Also, fix a few longstanding errors in little-used encoding conversion routines: win1251_to_iso, win866_to_iso, euc_tw_to_big5, euc_tw_to_mic, mic_to_euc_tw were all broken to varying extents. Patches by Tatsuo Ishii and Tom Lane. Thanks to Akio Ishida and Yasuo Ohgaki for identifying the security issues. |
||
---|---|---|
.. | ||
expected | ||
sql | ||
mbregress.sh | ||
README |
README for multibyte regression test 1998/7/22 Tatsuo Ishii This directory contains a set of tests for multibyte supporting extentions for PostgreSQL. To run the test, simply type: % mbregress.sh