aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeHashjoin.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2025-02-10 16:30:03 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2025-02-10 16:31:01 -0500
commite1f1b030d7d9fea27a77a335699372e0b222c61a (patch)
tree81f730278d03ddec27e5ca4dd7e404391cc63a35 /src/backend/executor/nodeHashjoin.c
parent4a6825c762112f085d6ee03bbce8e7abe2bf98e5 (diff)
downloadpostgresql-e1f1b030d7d9fea27a77a335699372e0b222c61a.tar.gz
postgresql-e1f1b030d7d9fea27a77a335699372e0b222c61a.zip
Adapt appendPsqlMetaConnect() to the new fmtId() encoding expectations.
We need to tell fmtId() what encoding to assume, but this function doesn't know that. Fortunately we can fix that without changing the function's API, because we can just use SQL_ASCII. That's because database names in connection requests are effectively binary not text: no encoding-aware processing will happen on them. This fixes XversionUpgrade failures seen in the buildfarm. The alternative of having pg_upgrade use setFmtEncoding() is unappetizing, given that it's connecting to multiple databases that may have different encodings. Andres Freund, Noah Misch, Tom Lane Security: CVE-2025-1094
Diffstat (limited to 'src/backend/executor/nodeHashjoin.c')
0 files changed, 0 insertions, 0 deletions