On Fri, Aug 04, 2006 at 11:58:22AM +0200, henka@xxxxxxxxxxxxx wrote: > > On Fri, Aug 04, 2006 at 10:48:17AM +0200, henka@xxxxxxxxxxxxx wrote: > > Two big questions: > > > > 1. What encoding are the two database (\l will tell you)? > > 2. What encoding are the clients expecting? > I've even tried using LATIN1 (ie, explicitly setting it to latin1 using > initdb, and then restoring the database after changing the 'utf-8' strings > in the dump data to 'latin1'). This still yields the funny chars. Wait, so the dump is in utf-8? You shouldn't need to edit the dump, postgresql will convert the encodings on the fly while loading. > To be honest, I have no idea what the origional encoding was. It should be in the dump file, almost the first line. Locale is of no interest to pg_dump, you'll have to decide how you want it. > Can you suggest any other approaches I can try to restore the database so > that those chars display correctly? Well, at the very least, does it go away if you type: set client_encoding=latin1; Please provide more details about your setup too, your client is on windows? The server is ...? Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to litigate.
Attachment:
signature.asc
Description: Digital signature