| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Tormod Omholt-Jensen <tormod(at)boostcom(dot)no> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Converting a database from LATIN1 to UTF-8 |
| Date: | 2006-03-27 11:42:25 |
| Message-ID: | 20060327114225.GE30791@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Mar 27, 2006 at 01:32:33PM +0200, Tormod Omholt-Jensen wrote:
> We are upgrading our systems to handle new languages and therefore we
> need to change the encoding of our postgres database from LATIN1 to UTF-8.
>
> I have pg_dumped the database and imported it into the new UTF-8 base.
> It seems like this worked just fine.
>
> Can anyone confirm that this is the correct way to do it?
Yep. The only thing you need to check is the clients connecting to the
database. They will start receving their output in UNICODE also. If
they don't want that they need to specify a default encoding.
Other than that your all set.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-03-27 11:52:39 | Re: When does a check constraint execute? |
| Previous Message | Martijn van Oosterhout | 2006-03-27 11:40:37 | Re: case insensitive match in unicode |