mirror of
https://github.com/postgres/postgres.git
synced 2026-02-22 01:11:05 -05:00
9dee1e4b38
This test previously used a data value containing U+0080, and would therefore fail if the database encoding didn't have an equivalent to that; which only about half of our supported server encodings do. We could fall back to using some plain-ASCII character, but that seems like it's losing most of the point of the test. Instead switch to using U+00A0 (no-break space), which translates into all our supported encodings except the four in the EUC_xx family. Per buildfarm testing. Back-patch to 9.1, which is as far back as this test is expected to succeed everywhere. (9.0 has the test, but without back-patching some 9.1 code changes we could not expect to get consistent results across platforms anyway.) |
||
|---|---|---|
| .. | ||
| plperl | ||
| plpgsql | ||
| plpython | ||
| tcl | ||
| Makefile | ||