This bug happens in SUSE 9.3 on both Pentium 4 and AMD64, whether the
binaries are from postgresql-8.0.1 RPMs on the SUSE 9.3 DVD or are
built from 8.0.3 source code. However this bug does NOT happen with a
Debian box (unstable) running 8.0.3 on an x86 (Athlon XP, whether
binary or built from source). The problem is Postgresql claims two
records has the same value for one string attribute that has a unique
constraint, while in fact the two string values are different. To see
this bug, just do a restore from the pg_dump'ed file attached to this
email. Sample steps and error message follow:
-------- begin command ---------------
createdb -E utf8 pg_bug
psql pg_bug < pg_dup_key_bug.dump
NOTICE: CREATE TABLE / UNIQUE will create implicit index
"gaocanusers_userid_key" for table "gaocanusers"
CREATE TABLE
ERROR: duplicate key violates unique constraint "gaocanusers_userid_key"
CONTEXT: COPY gaocanusers, line 2: "129406 ���ズ�
27324923@nowhere.com.kk f U\N \N \N \N -- f
2002-09-12 00:00:00 \N \\3031\\3..."
----------- end ------------
