> > Are you sure that the destination database has the same encoding > > declaration as the source did? > > That's what I'd be looking at - I had similar problems a few weeks ago. > See > this thread: > http://archives.postgresql.org/pgsql-admin/2007-12/msg00235.php I've been thinking about this, and while I don't agree it's a bug, I think that perhaps PostgreSQL should raise a notice or warning that the destination database has different encoding than the file being restored...? Obviously I'm not the only one (seemingly) caught out by this so I'm sure it would save some heartache for people. THINK BEFORE YOU PRINT - Save paper if you don't really need to print this *******************Confidentiality and Privilege Notice******************* The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email. Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments e-mail. ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
