Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id AB98F2E4116 for ; Sat, 9 Feb 2008 14:05:29 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 79775-01-2 for ; Sat, 9 Feb 2008 14:04:21 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2CA692E4160 for ; Sat, 9 Feb 2008 14:03:39 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m19I3bxV025531; Sat, 9 Feb 2008 13:03:37 -0500 (EST) To: "Mikel Lindsaar" cc: pgsql-admin@postgresql.org Subject: Re: Postgres Backup and Restore In-reply-to: <57a815bf0802090345p1c65fa12r622e4b4de062eb82@mail.gmail.com> References: <57a815bf0802090345p1c65fa12r622e4b4de062eb82@mail.gmail.com> Comments: In-reply-to "Mikel Lindsaar" message dated "Sat, 09 Feb 2008 22:45:40 +1100" Date: Sat, 09 Feb 2008 13:03:37 -0500 Message-ID: <25530.1202580217@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/118 X-Sequence-Number: 28192 "Mikel Lindsaar" writes: > If you have bad character encodings in your data, you can not backup > and restore that data using pg_dump and pg_restore, on Windows Server > 2003, using compress or plain text modes. Both modes fail on the bad > encoding when you try to restore. Are you sure that the destination database has the same encoding declaration as the source did? How was the badly-encoded data inserted in the first place? regards, tom lane