summaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/sql/postgres_fdw.sql
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2025-10-21 08:05:28 +0900
committerMichael Paquier <michael@paquier.xyz>2025-10-21 08:05:28 +0900
commit29b039e9166d5ad70b39375faceec2167343d355 (patch)
tree6bd944821e8abf5bdca4d7f4e9f0cd7ad4ba21c9 /contrib/postgres_fdw/sql/postgres_fdw.sql
parent4bea91f21f61d01bd40a4191a4a8c82d0959fffe (diff)
Fix POSIX compliance in pgwin32_unsetenv() for "name" argumentHEADorigin/masterorigin/HEADmaster
pgwin32_unsetenv() (compatibility routine of unsetenv() on Windows) lacks the input validation that its sibling pgwin32_setenv() has. Without these checks, calling unsetenv() with incorrect names crashes on WIN32. However, invalid names should be handled, failing on EINVAL. This commit adds the same checks as setenv() to fail with EINVAL for a "name" set to NULL, an empty string, or if '=' is included in the value, per POSIX requirements. Like 7ca37fb0406b, backpatch down to v14. pgwin32_unsetenv() is defined on REL_13_STABLE, but with the branch going EOL soon and the lack of setenv() there for WIN32, nothing is done for v13. Author: Bryan Green <dbryan.green@gmail.com> Discussion: https://postgr.es/m/b6a1e52b-d808-4df7-87f7-2ff48d15003e@gmail.com Backpatch-through: 14
Diffstat (limited to 'contrib/postgres_fdw/sql/postgres_fdw.sql')
0 files changed, 0 insertions, 0 deletions