The following bug has been logged online:

Bug reference: 1046
Logged by: Alfonso Baqueiro

Email address: abaqueirob (AT) hotmail (DOT) com

PostgreSQL version: 7.3.2

Operating system: Linux Redhat 9.0

Description: UNIQUE INDEX BUG

Details:

create table pru(
id integer not null primary key,
login varchar(10) unique not null
);

then when inserting values it says á = é = Ã* = ó = ú
(confuses different acuted vowels as if they were the same thing)

insert into pru (0, 'á');
-- no problem

But the error shows when trying the next:
insert into pru (1, 'é');
-- ERROR: cannot insert a duplicate key into unique index ...

Is a horrible bug that stops my migration from Centura SQLBase to PostgreSQL


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

"PostgreSQL Bugs List" <pgsql-bugs (AT) postgresql (DOT) org> writes:
Sounds to me like you have selected the wrong character set (encoding)
or wrong locale when installing the database. If Postgres thinks those
strings are equal, it is because the strcoll() library routine says so.
You need to pick a locale that will behave the way you want.

regards, tom lane

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

http://archives.postgresql.org