Re: Change server encoding after the fact

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Cody Caughlan <toolbag(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Change server encoding after the fact
Date: 2011-09-30 20:12:57
Message-ID: CAOR=d=22gbUR50yn2MPJ5WzOL6quS2KDqNiOdOOQ3UgGiWDWSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Sep 30, 2011 at 1:45 PM, Cody Caughlan <toolbag(at)gmail(dot)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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Cody Caughlan 2011-09-30 20:57:30 Re: Change server encoding after the fact
Previous Message Dario Beraldi 2011-09-30 19:53:14 Re: postgres for OLAP & data mining