diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2009-11-12 02:46:16 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2009-11-12 02:46:16 +0000 |
| commit | 8f8a5df694e7a012dfd762cb74d2083d83cf573b (patch) | |
| tree | 8e5d3ff2b64bb8243238dfc283f9f5b260f191a7 /src/backend/parser/parse_expr.c | |
| parent | 19d802767d7b9c37390c46d337e6558c0b60ea57 (diff) | |
| download | postgresql-8f8a5df694e7a012dfd762cb74d2083d83cf573b.tar.gz postgresql-8f8a5df694e7a012dfd762cb74d2083d83cf573b.zip | |
Make initdb behave sanely when the selected locale has codeset "US-ASCII".
Per discussion, this should result in defaulting to SQL_ASCII encoding.
The original coding could not support that because it conflated selection
of SQL_ASCII encoding with not being able to determine the encoding.
Adjust pg_get_encoding_from_locale()'s API to distinguish these cases,
and fix callers appropriately. Only initdb actually changes behavior,
since the other callers were perfectly content to consider these cases
equivalent.
Per bug #5178 from Boh Yap. Not going to bother back-patching, since
no one has complained before and there's an easy workaround (namely,
specify the encoding you want).
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions