dbTalk Databases Forums  

Re: [BUGS] B-tree unique index duplicate key error happens only in SUSE 9.3

mailing.database.pgsql-bugs mailing.database.pgsql-bugs


Discuss Re: [BUGS] B-tree unique index duplicate key error happens only in SUSE 9.3 in the mailing.database.pgsql-bugs forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
John Hansen
 
Posts: n/a

Default Re: [BUGS] B-tree unique index duplicate key error happens only in SUSE 9.3 - 06-19-2005 , 09:06 AM






FYI, Works just fine on gentoo with the UTF8 and ICU patches.

.... John

Quote:
This bug happens in SUSE 9.3 on both Pentium 4 and AMD64,=20
whether the binaries are from postgresql-8.0.1 RPMs on the=20
SUSE 9.3 DVD or are built from 8.0.3 source code. However=20
this bug does NOT happen with a Debian box (unstable) running=20
8.0.3 on an x86 (Athlon XP, whether binary or built from=20
source). The problem is Postgresql claims two records has the=20
same value for one string attribute that has a unique=20
constraint, while in fact the two string values are=20
different. To see this bug, just do a restore from the=20
pg_dump'ed file attached to this email. Sample steps and=20
error message follow:

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq


Reply With Quote
  #2  
Old   
Tom Lane
 
Posts: n/a

Default Re: [BUGS] B-tree unique index duplicate key error happens only in SUSE 9.3 - 06-19-2005 , 10:18 AM






Zhenlei Cai <jpenguin (AT) gmail (DOT) com> writes:
Quote:
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
What makes you think this is a Postgres bug, rather than a bug in the
locale definition you are using on the SUSE box? Try feeding the two
strings in question to strcoll() and see what happens.

One way that you can get inconsistent results from strcoll() is if you
feed it strings that are invalid according to the character set encoding
that strcoll() thinks you are using, which is to say the encoding
implied by the current LC_CTYPE locale setting. So it's possible that
the real problem is that you have Postgres' database encoding set to
something that's incompatible with the postmaster's LC_CTYPE locale.
(Try "show lc_ctype" to see what that is exactly.)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.