X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8F5593A202A for ; Fri, 5 Nov 2004 20:38:08 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52599-02 for ; Fri, 5 Nov 2004 20:37:59 +0000 (GMT) Received: from pepe.laptop.tld (unknown [196.40.30.116]) by svr1.postgresql.org (Postfix) with ESMTP id 110713A3E5B for ; Fri, 5 Nov 2004 20:37:59 +0000 (GMT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by pepe.laptop.tld (Postfix) with ESMTP id 3DAB640B22 for ; Fri, 5 Nov 2004 14:37:55 -0600 (CST) Message-ID: <418BE4A2.1060506@libby.com> Date: Fri, 05 Nov 2004 14:37:54 -0600 From: Dan Libby User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040815 X-Accept-Language: en-us, es, es-cr, en, sv, ja, ru MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: dump/restore results in duplicate key violation with 7.4.6. References: <418BD67D.1010108@osc.co.cr> In-Reply-To: <418BD67D.1010108@osc.co.cr> X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/55 X-Sequence-Number: 15440 Some more info... danda wrote: > So at this point I am mostly at a loss. I would have thought that > after changing the source DB to UNICODE encoding it should exhibit the > same behavior as the target. I can think of two explanations: > > 1: initdb does something with the encoding beyond setting > pg_database(encoding). > > 2: there is a bug in 7.4.6 that does not exist in 7.4.3 > > I suppose the next step is to create a new DB in 7.4.3 using UNICODE > and attempt to import the data in the same manner. But right now I > need a break. Okay, I tried the following test using the same input file on both machines. All steps identical. 1) create database test_enc with encoding = 'UNICODE'; 2) Create the schema for the 'category' table. 3) \i category_dump.sql It works on 7.4.3, but I get the duplicate key violation on 7.4.6. 7.4.3 is running on gentoo and was built with emerge postgresql. 7.4.6 is running on Redhat 9 and was built with ./configure --prefix=/var/lib/pgsql --with-python --with-perl I can probably come up with a clean test case using simplified data. I'm still hoping someone has the magical solution though... Dan Libby