| From: | Christian Fowler <spider(at)viovio(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christian Fowler <spider(at)viovio(dot)com>, pgsql-admin list <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: evil characters #bfef cause dump failure |
| Date: | 2004-11-15 20:44:20 |
| Message-ID: | Pine.LNX.4.61.0411151539540.12980@leda.steelsun.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)viovio(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-11-15 21:00:22 | Re: evil characters #bfef cause dump failure |
| Previous Message | Tom Lane | 2004-11-15 20:35:46 | Re: evil characters #bfef cause dump failure |