Is this a TODO? ---------------------------------------------------------------------------
Andrew Dunstan wrote: > Tom Lane wrote: > > >Peter Eisentraut <[EMAIL PROTECTED]> writes: > > > > > >>But the answer space is infinite: > >> > >> > > > > > > > >>$ LANG=C locale charmap > >>ANSI_X3.4-1968 > >> > >> > > > >Right, the hard part is mapping whatever weird string "locale charmap" > >chooses to return into one of the encodings our code knows about. > > > >HPUX seems to be just arbitrarily bizarre: > > > >$ LC_ALL=en_US.iso88591 locale charmap > >"iso88591.cm" > >$ LC_ALL=C.utf8 locale charmap > >"utf8.cm" > >$ > > > >As near as I can tell, the .cm is present in all the possible results; > >and why the quotes? > > > > > > > > > > > >>I suspect Japanese users will also have a problem with this mechanism, > >>but at least we could keep -E to override the automatic selection. > >> > >> > > > >Perhaps we could try to derive a setting from locale charmap, but barf > >and require explicit -E if we can't recognize it? > > > > > > > > Sounds like an excellent plan, at least for platforms that have such a > command. Windows does not appear to :-(. Are there other *nixes that > also lack it, or that also produce bizarre results like PH-UX? > > cheers > > andrew > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
