| From: | <Holger(dot)Friedrich-Fa-Trivadis(at)it(dot)nrw(dot)de> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Cc: | <adrian(dot)klaver(at)aklaver(dot)com> |
| Subject: | Re: logfile character encoding |
| Date: | 2014-08-18 13:31:32 |
| Message-ID: | C5DBACC6DCC7604C9E4875FD9C7968B1127857285D@ITXS01EVS.service.it.nrw.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
➢ Yeah, more digging on my part seems to indicate that no matter what you
➢ do Windows is going to set the locale to some variety of a codepage.
➢ Unfortunately, I do not use Windows enough to go much further with this.
➢ Hopefully someone more Microsoft fluent can weigh in on this, as this
➢ issue comes up periodically and it would be nice to have a definitive
➢ answer one way or another. I for one would appreciate the edification.
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)?
| From | Date | Subject | |
|---|---|---|---|
| Next 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 |
| Previous Message | Chris Hanks | 2014-08-18 12:36:01 | Re: Support functions for GiST index on citext |