On Fri, Sep 6, 2013 at 12:29 PM, Tom Lane wrote:
> Beena Emerson writes:
> > It still gives same result:
>
> > $ LANG=ko_KR LC_ALL=ko_KR
> > $ psql -d korean
>
> > korean=# SHOW client_encoding;
> > client_encoding
> > -
> > EUC_KR
> > (1 row)
>
> > korean=# INSERT INTO tbl VAL
On Fri, Sep 6, 2013 at 3:47 PM, Beena Emerson wrote:
>
>>
>> I wonder if you have tried changing your "locale" to ko_KR; something
>> like:
>>
>> LANG=ko_KR LC_ALL=ko_KR \
>> psql -d korean
>>
>
> Hi,
>
> It still gives same result:
>
> $ LANG=ko_KR LC_ALL=ko_KR
> $ psql -d korean
>
> korean=# SHO
Beena Emerson writes:
> It still gives same result:
> $ LANG=ko_KR LC_ALL=ko_KR
> $ psql -d korean
> korean=# SHOW client_encoding;
> client_encoding
> -
> EUC_KR
> (1 row)
> korean=# INSERT INTO tbl VALUES ('ê·¸ë ì¤');
> ERROR: invalid byte sequence for encoding "EUC_KR":
>
> I wonder if you have tried changing your "locale" to ko_KR; something like:
>
> LANG=ko_KR LC_ALL=ko_KR \
> psql -d korean
>
>
Hi,
It still gives same result:
$ LANG=ko_KR LC_ALL=ko_KR
$ psql -d korean
korean=# SHOW client_encoding;
client_encoding
-
EUC_KR
(1 row)
korean=
On Fri, Sep 6, 2013 at 2:56 PM, Beena Emerson wrote:
> Hello All,
>
> I am not able to understand how the encoding is handled. I would be happy if
> someone can tell what is happening in the following scenario:
>
> 1. I have created a database with EUC_KR encoding and created a table and
> inserte
