From: Dan Libby <dan@libby.com>
To: pgsql-admin@postgresql.org
Subject: Re: dump/restore results in duplicate key violation with 7.4.6.
Date: Fri, 05 Nov 2004 14:37:54 -0600
Message-ID: <418BE4A2.1060506@libby.com> (raw)
In-Reply-To: <418BD67D.1010108@osc.co.cr>
References: <418BD67D.1010108@osc.co.cr>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: dan@libby.com
Subject: Re: dump/restore results in duplicate key violation with 7.4.6.
In-Reply-To: <418BE4A2.1060506@libby.com>
References: <418BD67D.1010108@osc.co.cr> <418BE4A2.1060506@libby.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox