On Thu, Jul 1, 2010 at 9:44 AM, Sam Mason <sam@samason.me.uk> wrote:
> On Thu, Jul 01, 2010 at 09:31:12AM -0700, Mike Christensen wrote:
>> Then, I edited the file in Notepad and saved it as UTF8 which also
>> appears to have worked.
>
> I don't think you want to be doing this. The file should contain a "set
> client_encoding" of the correct value which will let PG to do the "right
> thing" when you import it back into a UTF8 database.
>
> --
> Sam http://samason.me.uk/
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
Yup, that fixed it. I had to change the DB.dbs.out file to use the
new encoding. Duh! Everything's working now.
Mike