| From: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | rod(at)iol(dot)ie, Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Table name with umlauts |
| Date: | 2010-11-22 19:54:03 |
| Message-ID: | AANLkTikZu2if1HC=yC3Kq0wk8rE-g6SPivO3xLNunBMm@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 22 November 2010 19:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I had the idea that the Windows version of psql was smart enough to
> set client_encoding based on the console encoding it finds itself
> running under, but I might be wrong about that. Or maybe you did
> something that overrode its default?
Apparently not:
Server [localhost]:
Database [postgres]:
Port [5432]:
Username [postgres]:
psql (8.4.5)
WARNING: Console code page (850) differs from Windows code page (1252)
8-bit characters might not work correctly. See psql reference
page "Notes for Windows users" for details.
Type "help" for help.
postgres=# show client_encoding;
client_encoding
-----------------
UTF8
(1 row)
postgres=#
--
Regards,
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2010-11-22 19:56:01 | Re: Table name with umlauts |
| Previous Message | anypossibility | 2010-11-22 19:41:30 | Debug advice when postgres connection maxing out |