Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 5F99C2E3416 for ; Sun, 10 Feb 2008 19:41:07 -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 19370-03 for ; Sun, 10 Feb 2008 19:40:57 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0A76A2E2DD6 for ; Sun, 10 Feb 2008 19:40:22 -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 m1ANeLaN011580; Sun, 10 Feb 2008 18:40:21 -0500 (EST) To: "Phillip Smith" cc: pgsql-admin@postgresql.org Subject: Re: Postgres Backup and Restore In-reply-to: <00ca01c86c38$a47b6de0$9b0014ac@wbaus090> References: <00ca01c86c38$a47b6de0$9b0014ac@wbaus090> Comments: In-reply-to "Phillip Smith" message dated "Mon, 11 Feb 2008 09:59:51 +1100" Date: Sun, 10 Feb 2008 18:40:21 -0500 Message-ID: <11579.1202686821@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/126 X-Sequence-Number: 28200 "Phillip Smith" writes: > 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...? If Postgres actually *knows* that the encodings are different, it can deal with that. The cases that are problematic are where the software has been misinformed for one reason or another. I doubt that a warning issued (or not) on the basis of misinformation will be especially helpful. regards, tom lane