Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 686BE650148 for ; Fri, 29 Aug 2008 10:34:55 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15458-05 for ; Fri, 29 Aug 2008 10:34:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 49206650138 for ; Fri, 29 Aug 2008 10:34:42 -0300 (ADT) Received: from commandprompt.com (CPE001b63afe888-CM001adea9c5a6.cpe.net.cable.rogers.com [99.236.211.160]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m7TDbjEo024524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 29 Aug 2008 06:37:48 -0700 Date: Fri, 29 Aug 2008 09:34:36 -0400 From: Andrew Sullivan To: pgsql-general@postgresql.org Subject: Re: Dumping/Restoring with constraints? Message-ID: <20080829133436.GG29463@commandprompt.com> Mail-Followup-To: Andrew Sullivan , pgsql-general@postgresql.org References: <48B5BC2A.5070104@wildenhain.de> <20080828174712.GB27283@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Fri, 29 Aug 2008 06:37:48 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/1110 X-Sequence-Number: 136940 On Fri, Aug 29, 2008 at 01:53:28PM +0800, Phoenix Kiula wrote: > My database encoding on BOTH the sides is UTF8. The dumped DB is UTF8. Are you sure? I know people asked up-thread for the output of \l, but I haven't seen it. If your encoding is UTF-8, then I don't understand how you got non-UTF-8 characters in there, unless there's some bug in the 8.2 series of which I'm unaware. > The one I am importing into is also UTF8. So why is it showing me this > error? Do I also have to look at stuff like "collation"? You shouldn't have to. That's a constraint on sorting and such like. It doesn't control what can get into the database. Hmm. I wonder if the problem is the locale you're using for pg_dump vs. what you're using when handing the data back in. If the locale were different, it might be possible that your client_encoding was different. I have no idea if this is the case, but you might want to try it. Check your locale at the command line on each system. > Also, how can I ensure that my dumped database on the server has only > UTF8 data? What constraint or function can I use? As I said before, if the database encoding is UTF-8, then it's supposed to be _impossible_ that you get non-UTF-8 data in there. That's the whole point of having the database encoding. A -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/