Re: evil characters #bfef cause dump failure
От | Christian Fowler |
---|---|
Тема | Re: evil characters #bfef cause dump failure |
Дата | |
Msg-id | Pine.LNX.4.61.0411151539540.12980@leda.steelsun.com обсуждение исходный текст |
Ответ на | Re: evil characters #bfef cause dump failure (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: evil characters #bfef cause dump failure
|
Список | pgsql-admin |
db-# ; server_encoding ----------------- SQL_ASCII (1 row) whoa! yikes, I bet this has a lot to do with it? I really wanted to keep everything UNICODE end-to-end. I must have forgotten --encoding on my initdb? Anything I can do at this point? On Mon, 15 Nov 2004, Tom Lane wrote: > Christian Fowler <spider@viovio.com> writes: >> [shell]$ env >> PGCLIENTENCODING=UNICODE >> LANG=en_US.UTF-8 > >> db=# \encoding >> UNICODE > > I was more concerned about the database encoding, which the above > doesn't prove. Try "SHOW server_encoding" > > regards, tom lane > [ \ / [ >X< Christian Fowler | spider AT viovio.com [ / \ http://www.viovio.com | http://www.tikipro.org
В списке pgsql-admin по дате отправления: