aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_target.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>1999-04-25 23:30:31 +0000
committerTom Lane <tgl@sss.pgh.pa.us>1999-04-25 23:30:31 +0000
commit26db818710f3e62234cfee0324046a33bc101392 (patch)
treea029905b3708d523fd51bede5c2df0d0186723f9 /src/backend/parser/parse_target.c
parentd69344c52022676ac0131eaf0d3f93a2fd10e74c (diff)
downloadpostgresql-26db818710f3e62234cfee0324046a33bc101392.tar.gz
postgresql-26db818710f3e62234cfee0324046a33bc101392.zip
It looks like the multibyte regress tests only work if both
the database encoding and the client encoding match the encoding expected by the test. So, force both of them to be set from the MULTIBYTE environment var. This allows regress tests to be run successfully in multibyte environments other than the compiled-in default.
Diffstat (limited to 'src/backend/parser/parse_target.c')
0 files changed, 0 insertions, 0 deletions