Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D82C12E3409 for ; Sun, 10 Feb 2008 20:28:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 72349-06 for ; Sun, 10 Feb 2008 20:28:37 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3128B2E33CE for ; Sun, 10 Feb 2008 20:28:37 -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 m1B0SZuq012051; Sun, 10 Feb 2008 19:28:36 -0500 (EST) To: "Phillip Smith" cc: pgsql-admin@postgresql.org Subject: Re: Postgres Backup and Restore In-reply-to: <00e401c86c40$9da2fb70$9b0014ac@wbaus090> References: <00e401c86c40$9da2fb70$9b0014ac@wbaus090> Comments: In-reply-to "Phillip Smith" message dated "Mon, 11 Feb 2008 10:56:55 +1100" Date: Sun, 10 Feb 2008 19:28:35 -0500 Message-ID: <12050.1202689715@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/129 X-Sequence-Number: 28203 "Phillip Smith" writes: > How has the software been misinformed and how can we avoid it then? :) Well, if that were entirely clear then we could fix it. > The start of the pgdump sets the client encoding, so shouldn't that tell PG > that things could get strange? The problems seem to arise when the data doesn't actually have the claimed encoding. We've been gradually tightening the encoding checks over the years, so data that older versions let pass without comment might now be recognized as malformed. In the OP's case there may be something else going on (such as an actual encoding-conversion bug). I've encouraged him to try to trace things forward from his original input data and see if we can find out exactly where it went off the rails. regards, tom lane