Re: Client Encoding and Latin characters

From: Lee Hachadoorian <lee(dot)hachadoorian(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Client Encoding and Latin characters
Date: 2009-11-24 17:03:28
Message-ID: 5ab13580911240903q1a1ce069m5eecc9d05aac225b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> Uh, no.  You can pretty much assume that LATIN1 will take any random
> byte string; likewise for any other single-byte encoding.  UTF8 as a
> default is a bit safer because it's significantly more likely that it
> will be able to detect non-UTF8 input.
>
>                        regards, tom lane
>

So, IIUC, the general approach is:

*Leave the default client_encoding = server_encoding (in this case UTF8)
*Rely on the client to change client_encoding on a session basis only

Thanks,
--Lee

--
Lee Hachadoorian
PhD Student, Geography
Program in Earth & Environmental Sciences
CUNY Graduate Center

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2009-11-24 17:14:53 Re: [HACKERS] Updating column on row update
Previous Message Andrej 2009-11-24 16:51:24 Re: ora2pg and DBD::Pg