| From: | Kai Borgolte <Kai(dot)Borgolte(at)gmx(dot)de> |
|---|---|
| To: | Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: logfile character encoding |
| Date: | 2014-08-18 14:51:31 |
| Message-ID: | 53F212F3.3000504@gmx.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 18.08.2014 15:31, schrieb Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de:
> Wikipedia says that UTF-8 is code page 65001, in Microsoft notation (see http://en.wikipedia.org/wiki/Code_page) Does this help in any way (i.e. does German_Germany.65001 work for you)?
No, I tried that value yesterday, see my answer to Adrian.
It seems Unicode encodings are just not target of Windows Locales. Which
in my opinion is reasonable: Why should it be a localization issue, how
a program writes Unicode to a file? When a localized Windows suggests
two different 8bit-charsets for usage (ANSI and OEM), this doesn't
hinder a program to write Unicode. Why can't PostgreSQL "Postmaster" do it?
--
Kai Borgolte, Bonn
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Redoute | 2014-08-18 15:00:05 | Re: logfile character encoding |
| Previous Message | Dorian Hoxha | 2014-08-18 14:28:23 | select top_countries and for each country, select top_cities in that country, in 1 query |