Thanks for your replay. The "0xe9ab99" is not SJIS nor SHIFT_JIS_2004. But I shoud export data with not regular SJIS character from old database(7.4.3) to new database(8.3), and use the old programe which export data as SJIS encoding .csv file. Can I modify conf file to ignore the error? or check inigore character from the database and convert it to regular SJIS encoding character with some tools ? And > >> to export data as .csv file, > >> I use set client_encoding='SJIS' at client. > > > > No, you should use UTF-8 of default. means export a UTF-8 encoding csv file? Thanks 2008/2/8, Hiroshi Saito <z-saito@xxxxxxxxxxxxxxxx>: > Ooops, shortage of information..sorry. > Please see, > http://winpg.jp/~saito/pg83/HASHIGODATA/ > > > Hi. > > > > ----- Original Message ----- > > From: "bh yuan" <bhyuan@xxxxxxxxx> > > > >> hi > >> > >> I used Postgresql7.4.3 with php for more than 3years. > >> Now I want to change my database to Postgresql8.3. > >> But I occur such problem > >> ---------------------------------------------------------- > >> ERROR: character 0xe9ab99 of encoding "UTF8" has no equivalent in "SJIS" > >> ERROR: character 0xe9ab99 of encoding "UTF8" has no equivalent in > >> "SHIFT_JIS_2004" > >> ---------------------------------------------------------- > >> The database was encoded by UTF-8, > > > > It SERVER_ENCODING=UTF-8 is Ok. > > > >> to export data as .csv file, > >> I use set client_encoding='SJIS' at client. > > > > No, you should use UTF-8 of default. > > > >> When I use Postgresql7.4.3,no problem occur, > > > > It seems that it has loose check.... > > > >> but after I chaged to Postgresql8.3 ,the error was occured. > >> > >> Can I ignore the error message ? > >> or any othe method to solve this problem. > > > > "0xe9ab99" which you use is famous UNICODE. > > Then, An error is right. (not SJIS) > > > > Regards, > > Hiroshi Saito > ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
