Re: Encoding Conversion - Mailing list pgsql-general

From jef peeraer
Subject Re: Encoding Conversion
Date
Msg-id 4460E9A2.9050208@pandora.be
Whole thread Raw
In response to Encoding Conversion  ("beer" <beer@cmu.edu>)
Responses Re: Encoding Conversion
List pgsql-general
beer schreef:
> Hello All
>
> So I have an old database that is ASCII_SQL encoded.  For a variety of reasons I need to convert the database to
UNICODE. I did some googling on this but have yet to find anything that looked like a viable option, so i thought I'd
postto the group and see what sort of advice might arise. :) 
well i recently struggled with the same problem. After a lot of trial
and error and reading, it seems that an ascii encoded database can't use
its client encoding capabilities ( set client_encoding to utf8 ).
i think the easist solution is to do a dump, recreate the database with
a proper encoding, and restore the dump.

jef peeraer
>
> TIA
>
> -b
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
>


pgsql-general by date:

Previous
From: John DeSoi
Date:
Subject: Re: default client_encoding with psql on windows
Next
From: Scott Lamb
Date:
Subject: Re: [PERFORM] Arguments Pro/Contra Software Raid