From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | rehak(at)sch(dot)bme(dot)hu |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: copy from stdin; bug? |
Date: | 2001-01-16 01:04:12 |
Message-ID: | 20010116100412F.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> yes, here are the output:
>
> datname |datdba|encoding|datpath
> -----------------+------+--------+-----------------
> template1 | 31| 5|template1
> map | 1003| 5|map
> helyes | 1003| 5|helyes
>
> i found that if i put a space behind the letters ([o with
> accent][a-z][\t]) before the tab, it works correct... but without the
> space it corrupt the database...
The encoding of your databases are all UNICODE. So you need to input
data as UTF-8 in this case. I guess you are trying to input ISO-8859-1
encoded data that is the source of the problem. Here are possible
solutions:
1) input data as UTF-8
2) crete a new databse using encoidng LATIN1. createdb -E LATIN1...
3) upgrade to 7.1 that has the capability to do an automatic
conversion between UTF-8 and ISO-8859-1.
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-16 01:14:10 | Re: Why is LockClassinfoForUpdate()'s mark4update a good idea? |
Previous Message | Hiroshi Inoue | 2001-01-16 00:50:37 | Re: Why is LockClassinfoForUpdate()'s mark4update a good idea? |