Re: Change server encoding after the fact - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Change server encoding after the fact
Date
Msg-id CAOR=d=22gbUR50yn2MPJ5WzOL6quS2KDqNiOdOOQ3UgGiWDWSA@mail.gmail.com
Whole thread Raw
In response to Re: Change server encoding after the fact  (Cody Caughlan <toolbag@gmail.com>)
Responses Re: Change server encoding after the fact  (Cody Caughlan <toolbag@gmail.com>)
List pgsql-general
On Fri, Sep 30, 2011 at 1:45 PM, Cody Caughlan <toolbag@gmail.com> wrote:
> That worked, but "file" shows no difference:
> $ iconv -f utf-8 -t utf-8 -c foo.sql > utf.sql
> $ file -i foo.sql
> foo.sql: text/plain; charset=us-ascii
> $file -i utf.sql
> utf.sql: text/plain; charset=us-ascii
> So iconv didnt actually convert the file OR does is the "file" command just
> ignorant?

Not sure.  try loading the dump into the UTF-8 DB in postgres and see
what happens I guess?

pgsql-general by date:

Previous
From: Dario Beraldi
Date:
Subject: Re: postgres for OLAP & data mining
Next
From: Cody Caughlan
Date:
Subject: Re: Change server encoding after the fact